all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Philipp Stephani <p.stephani2@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>, Philipp Stephani <phst@google.com>
Cc: Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: Silence two Clang warnings
Date: Thu, 15 Jun 2017 19:23:06 +0000	[thread overview]
Message-ID: <CAArVCkQOqTttuMP3qb-QRaLUUpz833=-qx_fp77qxdd9z9bugQ@mail.gmail.com> (raw)
In-Reply-To: <a536bbb0-c64b-3943-ba5e-dc58abae1a74@cs.ucla.edu>

[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]

Paul Eggert <eggert@cs.ucla.edu> schrieb am Do., 15. Juni 2017 um 20:56 Uhr:

> On 06/15/2017 06:11 AM, Philipp Stephani wrote:
> > Would you accept introducing pragmas to temporarily disable the
> > warnings in Clang (#pragma clang diagnostic push/ignore/pop), with an
> > explanation why they are false positives in these cases?
>
> That depends on what the warnings are and how useful they are elsewhere.
> These particular warnings do not seem to be useful for Emacs. For
> example, it is common practice in Emacs's C macros to parenthesize
> expressions to avoid operator-precedence confusion, and if Clang is
> complaining about the "extra" parentheses in the preprocessor output
> then that's clearly a warning that we should just shut off. Our goal is
> clarity and reliability, not Clang pacification.
>
>
Given that that message only appears with CFLAGS=-save-temps, we probably
don't need to disable it. With my usual configuration
(--enable-gcc-warnings, CFLAGS='-O0 -ggdb3') there are no warnings.

[-- Attachment #2: Type: text/html, Size: 1361 bytes --]

  reply	other threads:[~2017-06-15 19:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13 20:42 Silence two Clang warnings Paul Eggert
2017-06-15 13:11 ` Philipp Stephani
2017-06-15 18:56   ` Paul Eggert
2017-06-15 19:23     ` Philipp Stephani [this message]
2017-06-15 19:35       ` Paul Eggert
2017-06-16 16:53         ` Philipp Stephani

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAArVCkQOqTttuMP3qb-QRaLUUpz833=-qx_fp77qxdd9z9bugQ@mail.gmail.com' \
    --to=p.stephani2@gmail.com \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=phst@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.