public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/104890] [12 Regression] fails to build the 32bit libgcc on x86_64-linux-gnu (--enable-cet --with-arch-32=i686) Date: Sun, 13 Mar 2022 16:20:56 +0000 [thread overview] Message-ID: <bug-104890-4-fDL1kKUwfo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104890-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104890 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Comment on attachment 52619 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52619 A patch This looks wrong, it will fail with the same configuration if people build with -msse2. The question is why __attribute__((target ("general-regs-only"))) disables SHSTK. If that is intentional, we should change to what my first patch proposed, i.e. "no-sse" instead of "general-regs-only" (or "no-mmx,no-sse"). If it is unintentional, we should fix that.
next prev parent reply other threads:[~2022-03-13 16:20 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-12 10:43 [Bug target/104890] New: [12 Regression] fails to build the 32bit libgcc on x86_64-linux-gnu doko at gcc dot gnu.org 2022-03-12 10:50 ` [Bug target/104890] " doko at gcc dot gnu.org 2022-03-12 15:37 ` [Bug target/104890] [12 Regression] fails to build the 32bit libgcc on x86_64-linux-gnu (--enable-default-pie) hjl.tools at gmail dot com 2022-03-13 4:39 ` doko at gcc dot gnu.org 2022-03-13 4:39 ` doko at gcc dot gnu.org 2022-03-13 5:07 ` doko at gcc dot gnu.org 2022-03-13 15:53 ` [Bug target/104890] [12 Regression] fails to build the 32bit libgcc on x86_64-linux-gnu (--enable-cet) hjl.tools at gmail dot com 2022-03-13 16:17 ` [Bug target/104890] [12 Regression] fails to build the 32bit libgcc on x86_64-linux-gnu (--enable-cet --with-arch-32=i686) hjl.tools at gmail dot com 2022-03-13 16:17 ` hjl.tools at gmail dot com 2022-03-13 16:20 ` jakub at gcc dot gnu.org [this message] 2022-03-13 16:26 ` hjl.tools at gmail dot com 2022-03-13 18:09 ` hjl.tools at gmail dot com 2022-03-14 2:08 ` doko at gcc dot gnu.org 2022-03-14 8:35 ` rguenth at gcc dot gnu.org 2022-03-14 20:45 ` hjl.tools at gmail dot com 2022-03-15 9:24 ` cvs-commit at gcc dot gnu.org 2022-03-16 13:31 ` cvs-commit at gcc dot gnu.org 2022-03-16 13:32 ` hjl.tools at gmail dot com 2022-03-21 4:27 ` [Bug target/104890] [11 Regression] <x86gprintrin.h> doesn't work with __attribute__((target ("general-regs-only"))) and -march=i686 hjl.tools at gmail dot com 2022-03-21 4:31 ` hjl.tools at gmail dot com 2022-03-22 16:31 ` cvs-commit at gcc dot gnu.org 2022-03-22 16:34 ` 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-104890-4-fDL1kKUwfo@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).