public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/103762] [12 Regression] glibc master branch is miscompiled by r12-897 Date: Sat, 18 Dec 2021 22:44:58 +0000 [thread overview] Message-ID: <bug-103762-4-gIE7Gpvjw6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103762-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103762 Florian Weimer <fw at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fw at gcc dot gnu.org --- Comment #9 from Florian Weimer <fw at gcc dot gnu.org> --- glibc cannot easily work around such unexpected relocations for static or hidden variables. Static PIE currently requires PI_STATIC_AND_HIDDEN, and with the GCC 12 behavior, x86 would not be a PI_STATIC_AND_HIDDEN target anymore. This really has to be fixed in GCC. It's also important to avoid such runtime relocations for PIE startup time.
next prev parent reply other threads:[~2021-12-18 22:44 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-18 14:01 [Bug middle-end/103762] New: " hjl.tools at gmail dot com 2021-12-18 14:01 ` [Bug middle-end/103762] " hjl.tools at gmail dot com 2021-12-18 14:16 ` hjl.tools at gmail dot com 2021-12-18 14:25 ` hjl.tools at gmail dot com 2021-12-18 14:35 ` hjl.tools at gmail dot com 2021-12-18 15:17 ` hjl.tools at gmail dot com 2021-12-18 16:27 ` hjl.tools at gmail dot com 2021-12-18 18:48 ` hjl.tools at gmail dot com 2021-12-18 19:18 ` jakub at gcc dot gnu.org 2021-12-18 19:28 ` hjl.tools at gmail dot com 2021-12-18 22:44 ` fw at gcc dot gnu.org [this message] 2021-12-18 23:01 ` [Bug rtl-optimization/103762] " hjl.tools at gmail dot com 2021-12-19 20:10 ` [Bug target/103762] " hjl.tools at gmail dot com 2021-12-27 13:33 ` cvs-commit at gcc dot gnu.org 2021-12-27 13:35 ` hjl.tools at gmail dot com
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-103762-4-gIE7Gpvjw6@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).