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 rtl-optimization/104777] [9/10/11/12 Regression] gcc crashes while compiling a custom coroutine library sample Date: Sat, 05 Mar 2022 22:07:17 +0000 [thread overview] Message-ID: <bug-104777-4-9adomyFVBd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104777-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104777 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work|8.5.0 |8.1.0, 8.3.0 Known to fail| |8.4.0, 8.5.0 --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Note loop being a thread_local (__thread) is important here to get the crash. Further reduced testcase: int savestate_r; int savestate_ssb; extern void abort(); __thread int loop; void f (void) { int savestate_r0_5; int savestate_r1_6; __asm__("" : "=m" (savestate_ssb), "=r" (savestate_r)); savestate_r0_5 = savestate_r; if (savestate_r0_5 == 0) { __asm__ __volatile__("" : : "m" (loop)); abort (); } __asm__("" : "=m" (savestate_ssb), "=r" (savestate_r)); savestate_r1_6 = savestate_r; if (savestate_r1_6 != 0) return; __asm__ __volatile__("" : : "m" (loop)); abort (); }
next prev parent reply other threads:[~2022-03-05 22:07 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-04 7:45 [Bug c++/104777] New: " janezz55 at gmail dot com 2022-03-04 12:54 ` [Bug c++/104777] " marxin at gcc dot gnu.org 2022-03-04 15:44 ` [Bug c++/104777] gcc crashes while compiling a custom coroutine library sample since r10-5137-g43aae289866f5ea5 marxin at gcc dot gnu.org 2022-03-04 15:51 ` mpolacek at gcc dot gnu.org 2022-03-05 21:44 ` [Bug c++/104777] [10/11/12 Regression] " pinskia at gcc dot gnu.org 2022-03-05 21:45 ` [Bug rtl-optimization/104777] " pinskia at gcc dot gnu.org 2022-03-05 21:55 ` [Bug rtl-optimization/104777] [9/10/11/12 Regression] gcc crashes while compiling a custom coroutine library sample pinskia at gcc dot gnu.org 2022-03-05 21:55 ` pinskia at gcc dot gnu.org 2022-03-05 22:07 ` pinskia at gcc dot gnu.org [this message] 2022-03-08 0:07 ` mpolacek at gcc dot gnu.org 2022-03-08 19:00 ` cvs-commit at gcc dot gnu.org 2022-03-08 19:01 ` [Bug rtl-optimization/104777] [9/10/11 " mpolacek at gcc dot gnu.org 2022-03-10 18:33 ` cvs-commit at gcc dot gnu.org 2022-03-10 18:34 ` [Bug rtl-optimization/104777] [9/10 " mpolacek at gcc dot gnu.org 2022-06-13 10:04 ` ubizjak at gmail dot com 2022-06-13 12:00 ` ubizjak at gmail dot com 2022-06-13 12:19 ` stsp at users dot sourceforge.net 2022-06-13 13:26 ` jakub at gcc dot gnu.org 2022-06-13 14:39 ` mpolacek at gcc dot gnu.org 2022-06-13 16:29 ` cvs-commit at gcc dot gnu.org 2022-06-13 16:30 ` mpolacek 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-104777-4-9adomyFVBd@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).