public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/104446] [9/10/11/12 Regression] ICE in trunc_int_for_mode, at explow.cc:59 Date: Tue, 08 Feb 2022 21:37:19 +0000 [thread overview] Message-ID: <bug-104446-4-VDHHd2UMLL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104446-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104446 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |needs-bisection Known to fail| |11.2.0, 9.1.0 Status|UNCONFIRMED |NEW Last reconfirmed| |2022-02-08 Known to work| |8.1.0 Target Milestone|--- |9.5 Ever confirmed|0 |1 Component|c |middle-end --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Confirmed reduced testcase w/o -finstrument-functions: That is only -O2 -m32 -mrtd is needed to produce the ICE. register volatile int a __asm__("%esp"); void f(void*); void f1(void*); void t () { f(__builtin_return_address(0)); a = 0; f1(__builtin_return_address(0)); } ---- CUT --- Note this works with the C++ front-end for some reason.
next prev parent reply other threads:[~2022-02-08 21:37 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-08 19:40 [Bug c/104446] New: " gscfq@t-online.de 2022-02-08 21:37 ` pinskia at gcc dot gnu.org [this message] 2022-02-09 7:32 ` [Bug middle-end/104446] " rguenth at gcc dot gnu.org 2022-02-09 9:04 ` [Bug middle-end/104446] [9/10/11/12 Regression] ICE in trunc_int_for_mode, at explow.cc:59 since r9-6999 jakub at gcc dot gnu.org 2022-02-09 11:13 ` jakub at gcc dot gnu.org 2022-02-09 11:32 ` jakub at gcc dot gnu.org 2022-02-10 7:47 ` segher at gcc dot gnu.org 2022-02-11 12:52 ` cvs-commit at gcc dot gnu.org 2022-02-11 12:53 ` [Bug middle-end/104446] [9/10/11 " jakub at gcc dot gnu.org 2022-02-19 8:02 ` cvs-commit at gcc dot gnu.org 2022-02-19 8:08 ` [Bug middle-end/104446] [9/10 " jakub at gcc dot gnu.org 2022-05-10 8:23 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:24 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:36 ` jakub 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-104446-4-VDHHd2UMLL@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: linkBe 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).