public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paulbendixen at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113156] AVR build broken due to ICE while compiling libgcc, started with r14-6201-gf0a90c7d7333fc
Date: Thu, 04 Jan 2024 22:04:12 +0000 [thread overview]
Message-ID: <bug-113156-4-MyNPLXcDwz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113156-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113156
Paul M. Bendixen <paulbendixen at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |paulbendixen at gmail dot com
--- Comment #3 from Paul M. Bendixen <paulbendixen at gmail dot com> ---
I can confirm this also happens for me.
I have found the same commit to be the problem and have tried with both gcc 11
and 12
gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0
For reproducability it was configured using:
../configure --prefix=$PREFIX --target=avr --enable-languages=c,c++
--disable-nls --disable-libssp --with-dwarf2
The error only seems to happen when compiling the long64 part of the multilib
(or at least first), the parts compiled for avrXX and xmegaX targets run fine.
next prev parent reply other threads:[~2024-01-04 22:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 9:03 [Bug target/113156] New: " dimitar at gcc dot gnu.org
2023-12-27 9:11 ` [Bug target/113156] " pinskia at gcc dot gnu.org
2023-12-27 9:14 ` pinskia at gcc dot gnu.org
2024-01-04 22:04 ` paulbendixen at gmail dot com [this message]
2024-01-08 14:10 ` [Bug target/113156] [14 Regression] " rguenth at gcc dot gnu.org
2024-01-10 5:08 ` pinskia at gcc dot gnu.org
2024-01-10 5:11 ` pinskia at gcc dot gnu.org
2024-01-10 5:12 ` [Bug target/113156] [11/12/13/14 " pinskia at gcc dot gnu.org
2024-01-10 5:22 ` pinskia at gcc dot gnu.org
2024-01-10 9:18 ` gjl at gcc dot gnu.org
2024-01-10 9:23 ` pinskia at gcc dot gnu.org
2024-01-10 11:18 ` gjl at gcc dot gnu.org
2024-01-11 0:13 ` pinskia at gcc dot gnu.org
2024-01-15 9:42 ` cvs-commit at gcc dot gnu.org
2024-01-15 11:43 ` cvs-commit at gcc dot gnu.org
2024-01-15 11:49 ` cvs-commit at gcc dot gnu.org
2024-01-15 13:26 ` gjl at gcc dot gnu.org
2024-01-16 22:44 ` pinskia at gcc dot gnu.org
2024-01-17 8:29 ` gjl 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-113156-4-MyNPLXcDwz@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).