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/113156] [11/12/13/14 Regression] AVR build broken due to ICE while compiling libgcc, started with r14-6201-gf0a90c7d7333fc
Date: Wed, 10 Jan 2024 05:12:56 +0000	[thread overview]
Message-ID: <bug-113156-4-te9DMYOeLi@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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to fail|                            |11.1.0
      Known to work|                            |10.1.0
            Summary|[14 Regression] AVR build   |[11/12/13/14 Regression]
                   |broken due to ICE while     |AVR build broken due to ICE
                   |compiling libgcc, started   |while compiling libgcc,
                   |with                        |started with
                   |r14-6201-gf0a90c7d7333fc    |r14-6201-gf0a90c7d7333fc

--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The testcase fails with GCC 11+ with -fchecking .

  parent reply	other threads:[~2024-01-10  5:12 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
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 ` pinskia at gcc dot gnu.org [this message]
2024-01-10  5:22 ` [Bug target/113156] [11/12/13/14 " 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-te9DMYOeLi@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).