From: Alan Modra <amodra@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Jan Beulich <jbeulich@suse.com>, binutils@sourceware.org
Subject: Re: strange segfault i386-dis.c:9815:28
Date: Mon, 20 Mar 2023 09:14:45 +1030 [thread overview]
Message-ID: <ZBeQXTIBjGj8TLBr@squeak.grove.modra.org> (raw)
In-Reply-To: <CAMe9rOpn5KPqjUBi0EfWM4imU8baRv2ivZLMr=Lu2QzZCF8rSg@mail.gmail.com>
On Fri, Mar 17, 2023 at 08:56:25AM -0700, H.J. Lu wrote:
> Compilers should handle local variables with setjmp properly.
> Without a testcase, it is hard to tell what really went wrong.
gcc might do so, because it recognises setjmp as special. Does clang?
What about other compilers? I'm going to apply the patch I posted.
Making accesses to "ins" and "priv" go via volatile pointer in the
longjmp return path has minimal effect on performance.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2023-03-19 22:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 10:41 Alan Modra
2023-03-17 15:56 ` H.J. Lu
2023-03-17 17:09 ` Andreas Schwab
2023-03-19 22:44 ` Alan Modra [this message]
2023-03-20 7:29 ` Jan Beulich
2023-03-20 7:57 ` Alan Modra
2023-03-20 10:26 ` Alan Modra
2023-03-20 10:41 ` Jan Beulich
2023-03-23 12:59 ` Alan Modra
2023-04-04 7:03 ` Jan Beulich
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=ZBeQXTIBjGj8TLBr@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=jbeulich@suse.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).