public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/103860] [9/10/11/12 Regression] wrong code at -O3 with -fPIC on x86_64-linux-gnu Date: Wed, 29 Dec 2021 19:43:05 +0000 [thread overview] Message-ID: <bug-103860-4-tBDJdtNTF0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103860-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103860 --- Comment #5 from Segher Boessenkool <segher at gcc dot gnu.org> --- That looks good. But can you always set maybe_check_pro to true (and then optimise it away of course)?
next prev parent reply other threads:[~2021-12-29 19:43 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-29 16:08 [Bug tree-optimization/103860] New: " zhendong.su at inf dot ethz.ch 2021-12-29 17:17 ` [Bug rtl-optimization/103860] [9/10/11/12 Regression] " jakub at gcc dot gnu.org 2021-12-29 17:32 ` jakub at gcc dot gnu.org 2021-12-29 18:10 ` jakub at gcc dot gnu.org 2021-12-29 18:23 ` jakub at gcc dot gnu.org 2021-12-29 19:43 ` segher at gcc dot gnu.org [this message] 2021-12-29 19:58 ` jakub at gcc dot gnu.org 2021-12-29 20:30 ` segher at gcc dot gnu.org 2021-12-30 13:24 ` cvs-commit at gcc dot gnu.org 2021-12-30 13:39 ` [Bug rtl-optimization/103860] [9/10/11 " jakub at gcc dot gnu.org 2022-01-04 9:13 ` cvs-commit at gcc dot gnu.org 2022-01-04 13:59 ` rguenth at gcc dot gnu.org 2022-01-24 9:20 ` cvs-commit at gcc dot gnu.org 2022-01-24 9:30 ` [Bug rtl-optimization/103860] [9/10 " jakub at gcc dot gnu.org 2022-05-10 8:22 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:23 ` 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-103860-4-tBDJdtNTF0@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).