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 tree-optimization/109164] thread_local initialization error with -ftree-pre Date: Thu, 16 Mar 2023 23:25:59 +0000 [thread overview] Message-ID: <bug-109164-4-gXtwBdKquK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109164-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109164 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|thread_local initialization |thread_local initialization |error with -ftree-pre |error with -ftree-pre |-foptimize-sibling-calls | Known to fail| |11.3.0 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Here is a testcase which fails at `-O1 -ftree-pre` and does not need `-foptimize-sibling-calls`: struct Struct { virtual void virtual_func(); }; extern thread_local Struct& thread_local_ref; bool other_func(void); bool test_func(void) { while (1) { thread_local_ref.virtual_func(); if (!other_func()) return 0; } }
next prev parent reply other threads:[~2023-03-16 23:25 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-16 23:09 [Bug c++/109164] New: aarch64 thread_local initialization error with -ftree-pre and -foptimize-sibling-calls loganh at synopsys dot com 2023-03-16 23:25 ` pinskia at gcc dot gnu.org [this message] 2023-03-16 23:29 ` [Bug tree-optimization/109164] thread_local initialization error with -ftree-pre pinskia at gcc dot gnu.org 2023-03-16 23:31 ` pinskia at gcc dot gnu.org 2023-03-17 10:12 ` [Bug c++/109164] wrong code with thread_local reference, loops and -ftree-pre rguenth at gcc dot gnu.org 2023-03-17 12:01 ` jakub at gcc dot gnu.org 2023-03-20 19:32 ` cvs-commit at gcc dot gnu.org 2023-03-20 19:36 ` jakub at gcc dot gnu.org 2023-04-18 7:15 ` cvs-commit at gcc dot gnu.org 2023-05-02 20:16 ` cvs-commit at gcc dot gnu.org 2023-05-03 15:22 ` cvs-commit at gcc dot gnu.org 2023-05-04 7:26 ` 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-109164-4-gXtwBdKquK@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).