public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112640] [14 regression] Failed bootstrap on arm64 (libgcc/config/libbid/bid128_fma.c:3569:1: internal compiler error: in extract_base_offset_in_addr, at config/aarch64/aarch64.cc:26424)
Date: Mon, 20 Nov 2023 19:28:45 +0000 [thread overview]
Message-ID: <bug-112640-4-nynqnT5FL9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112640-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112640
--- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Sam James from comment #7)
> # head -10 /proc/cpuinfo
> processor : 0
> BogoMIPS : 50.08
> Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp
> asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
> CPU implementer : 0x41
> CPU architecture: 8
> CPU variant : 0x3
> CPU part : 0xd0c
> CPU revision : 1
That correspondes to `-mcpu=neoverse-n1`:
AARCH64_CORE("neoverse-n1", neoversen1, cortexa57, V8_2A, (F16, RCPC,
DOTPROD, PROFILE), neoversen1, 0x41, 0xd0c, -1)
next prev parent reply other threads:[~2023-11-20 19:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 14:46 [Bug target/112640] New: " sjames at gcc dot gnu.org
2023-11-20 14:47 ` [Bug target/112640] " sjames at gcc dot gnu.org
2023-11-20 14:49 ` pinskia at gcc dot gnu.org
2023-11-20 14:50 ` sjames at gcc dot gnu.org
2023-11-20 15:29 ` sjames at gcc dot gnu.org
2023-11-20 15:43 ` sjames at gcc dot gnu.org
2023-11-20 16:29 ` jakub at gcc dot gnu.org
2023-11-20 19:19 ` pinskia at gcc dot gnu.org
2023-11-20 19:24 ` sjames at gcc dot gnu.org
2023-11-20 19:28 ` pinskia at gcc dot gnu.org [this message]
2023-11-20 19:30 ` pinskia at gcc dot gnu.org
2023-11-30 12:16 ` [Bug target/112640] [14 regression] Failed profiledbootstrap " jakub at gcc dot gnu.org
2023-12-01 1:13 ` sjames at gcc dot gnu.org
2024-03-06 16:43 ` sjames 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-112640-4-nynqnT5FL9@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).