public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "franke at computer dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/108673] ICE with -fstack-clash-protection and noreturn attribute on x86_64-w64-mingw32
Date: Sat, 04 Feb 2023 15:49:45 +0000 [thread overview]
Message-ID: <bug-108673-4-jTX4ItFFqx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108673-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108673
Christian Franke <franke at computer dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |franke at computer dot org
--- Comment #1 from Christian Franke <franke at computer dot org> ---
Could also be reproduced with x86_64-pc-cygwin-gcc 11.3.0 and
x86_64-w64-mingw32-gcc 11.3.0 from current Cygwin distribution:
$ gcc -O1 -fstack-clash-protection -S f.c
during RTL pass: final
x.c: In function ‘foo’:
x.c:5:1: internal compiler error: in seh_emit_stackalloc, at
config/i386/winnt.c:1056
5 | }
| ^
...
The error does not occur if -fipa-pure-const ("Discover which functions are
pure or constant") is disabled:
$ gcc -O3 -fno-ipa-pure-const -fstack-clash-protection -S f.c; echo $?
0
Assembly output looks sane then.
next prev parent reply other threads:[~2023-02-04 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 13:03 [Bug target/108673] New: " lh_mouse at 126 dot com
2023-02-04 15:49 ` franke at computer dot org [this message]
2023-02-04 20:22 ` [Bug target/108673] " pinskia at gcc dot gnu.org
2023-02-14 17:12 ` amy.mclaughlin at iar dot com
2023-02-14 18:01 ` franke at computer dot org
2023-02-14 18:11 ` ebotcazou at gcc dot gnu.org
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=bug-108673-4-jTX4ItFFqx@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).