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 c/109765] [14 regression] ICE in real_to_decimal_for_mode Date: Sun, 07 May 2023 22:42:34 +0000 [thread overview] Message-ID: <bug-109765-4-sHkzIqy5FK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109765-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109765 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target| |aarch64-unknown-linux-gnu --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- I just built for aarch64 last night and I can't reproduce this. ubuntu@ubuntu:~/src/upstream-gcc-aarch64/gcc\# ~/upstream-gcc/bin/gcc -v Using built-in specs. COLLECT_GCC=/home/ubuntu/upstream-gcc/bin/gcc COLLECT_LTO_WRAPPER=/home/ubuntu/upstream-gcc/libexec/gcc/aarch64-unknown-linux-gnu/14.0.0/lto-wrapper Target: aarch64-unknown-linux-gnu Configured with: /home/ubuntu/src/upstream-gcc-aarch64/gcc/configure --prefix=/home/ubuntu/upstream-gcc --enable-languages=c,c++,fortran,lto,objc,go,rust Thread model: posix Supported LTO compression algorithms: zlib gcc version 14.0.0 20230507 (experimental) [master f2c31b4c1e2] (GCC) r14-553-g2c8fa77120b48b4682f423 plus the patch for r14-558-ga1a9ce2441df0675 .
next prev parent reply other threads:[~2023-05-07 22:42 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-07 22:25 [Bug c/109765] New: " sjames at gcc dot gnu.org 2023-05-07 22:42 ` pinskia at gcc dot gnu.org [this message] 2023-05-07 22:49 ` [Bug bootstrap/109765] " pinskia at gcc dot gnu.org 2023-05-07 23:25 ` pinskia at gcc dot gnu.org 2023-05-08 5:15 ` sjames at gcc dot gnu.org 2023-05-08 5:23 ` pinskia at gcc dot gnu.org 2023-05-09 23:08 ` 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-109765-4-sHkzIqy5FK@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).