all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Pip Cet <pipcet@protonmail.com>, Andrea Corallo <acorallo@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: master 8c81818673a 6/7: Tune volatile in read_char
Date: Sat, 17 Aug 2024 11:16:46 -0700	[thread overview]
Message-ID: <d4ac2373-9fb4-4e30-a1ee-9dbf547ea950@cs.ucla.edu> (raw)
In-Reply-To: <87zfpbgjz7.fsf@protonmail.com>

On 2024-08-17 10:03, Pip Cet wrote:

> I think GCC, by its own logic, is right about this one. It doesn't know
> that local_getcjmp is local (and hasn't escaped), so it would be, in
> theory, possible for a signal handler to call 'longjmp' before
> c_volatile is initialized.

For what it's worth, gcc (GCC) 14.2.1 20240801 (Red Hat 14.2.1-1) does 
not issue the warning on x86-64, when Emacs is built with 
--enable-gcc-warnings. Either it's smarter about escaping, or it figures 
it's not worth issuing warnings about what random signal handlers might 
do, or (most likely) it's just the luck of that particular configuation.

Thanks for the patch; I installed it.


> I still think we should default to -Werror=clobbered to catch distributors
> performing LTO builds and such.

Not sure that'd be wise given the false positive that your patch fixes, 
More false positives are likely lurking in other GCC setups, and 
defaulting to -Werror=clobbered would likely break builds due to false 
alarms.



  reply	other threads:[~2024-08-17 18:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <172386820621.30556.15409337288904485218@vcs2.savannah.gnu.org>
     [not found] ` <20240817041648.A6687C2BC66@vcs2.savannah.gnu.org>
2024-08-17 15:04   ` master 8c81818673a 6/7: Tune volatile in read_char Andrea Corallo
2024-08-17 17:03     ` Pip Cet
2024-08-17 18:16       ` Paul Eggert [this message]
2024-08-17 18:17     ` Paul Eggert
2024-08-18  7:39       ` Andrea Corallo
2024-08-18 21:39         ` Paul Eggert
2024-08-18 21:57           ` Sam James
2024-08-18 22:03             ` Paul Eggert
2024-08-19 14:43           ` Andrea Corallo
2024-08-19 15:01             ` Eli Zaretskii
2024-08-19 15:32               ` Pip Cet
2024-08-19 15:44                 ` Eli Zaretskii
2024-08-19 16:01                   ` Pip Cet
2024-08-19 16:15                     ` Eli Zaretskii
2024-08-19 18:59                       ` Paul Eggert
2024-08-19 19:27                         ` Eli Zaretskii
2024-08-19 19:05                       ` Pip Cet
2024-08-19 19:29                         ` Eli Zaretskii
2024-08-19 19:43                           ` Paul Eggert
2024-08-19 20:08                             ` Pip Cet
2024-08-19 22:20                               ` Paul Eggert
2024-08-19 23:40                                 ` Pip Cet

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=d4ac2373-9fb4-4e30-a1ee-9dbf547ea950@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=acorallo@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=pipcet@protonmail.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.