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 target/109007] building for POWER8 leaks into POWER9 ISA with g++ 11.3 (cross-compiler on x86_64 host) Date: Sun, 05 Mar 2023 21:40:49 +0000 [thread overview] Message-ID: <bug-109007-4-RJCLZXpaz8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109007-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109007 --- Comment #17 from Segher Boessenkool <segher at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #16) > Or just make sure the libraries are still built with -mcpu=power8 even when > the compiler defaults to something else. That doesn't scale. > That said, neither multilibs nor just making sure libraries are built with > -mcpu=power8 can help with libraries outside of gcc (unless they are built > as multilibs or with the extra flags). Sure. But this bug is about that a compiler built --with-cpu=X can not build anything that can run on any older CPU (or does not have some feature that X has, more generally). This is a problem that we already do have a solution for, but something we have disabled in the powerpc64le-linux subtarget unfortunately. > or build gcc and all the needed libraries yourself. Yup. But it should not be necessary to build a different GCC.
next prev parent reply other threads:[~2023-03-05 21:40 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-03 11:58 [Bug target/109007] New: " bugreporter66 at gmail dot com 2023-03-03 18:23 ` [Bug target/109007] " jakub at gcc dot gnu.org 2023-03-03 20:24 ` pinskia at gcc dot gnu.org 2023-03-04 6:47 ` bugreporter66 at gmail dot com 2023-03-04 9:56 ` bugreporter66 at gmail dot com 2023-03-04 9:58 ` bugreporter66 at gmail dot com 2023-03-04 10:10 ` jakub at gcc dot gnu.org 2023-03-04 10:36 ` bugreporter66 at gmail dot com 2023-03-04 10:40 ` bugreporter66 at gmail dot com 2023-03-04 10:49 ` jakub at gcc dot gnu.org 2023-03-04 11:24 ` bugreporter66 at gmail dot com 2023-03-04 11:30 ` jakub at gcc dot gnu.org 2023-03-04 21:12 ` bugreporter66 at gmail dot com 2023-03-04 22:02 ` segher at gcc dot gnu.org 2023-03-05 15:31 ` bugreporter66 at gmail dot com 2023-03-05 18:59 ` segher at gcc dot gnu.org 2023-03-05 20:07 ` jakub at gcc dot gnu.org 2023-03-05 21:40 ` segher at gcc dot gnu.org [this message] 2023-03-06 11:06 ` bugreporter66 at gmail dot com 2023-03-06 11:19 ` bugreporter66 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-109007-4-RJCLZXpaz8@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).