public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bugreporter66 at gmail dot com" <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: Sat, 04 Mar 2023 11:24:05 +0000	[thread overview]
Message-ID: <bug-109007-4-EmSsZ2F54w@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 #10 from bugreporter66 at gmail dot com ---
Yes, it seems so. They've switched to POWER9 by default in Ubuntu 22.04, so it
means that gcc itself (along with standard libraries) was compiled for POWER9
as well. It used to be POWER8 in the previous releases.

  parent reply	other threads:[~2023-03-04 11:24 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 [this message]
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
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-EmSsZ2F54w@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: link
Be 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).