public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87281] qsort checking ICE in ia64_reorg building libgo
Date: Thu, 02 Nov 2023 22:36:45 +0000	[thread overview]
Message-ID: <bug-87281-4-zYyBqd13wh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-87281-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87281

--- Comment #15 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Created attachment 56496
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56496&action=edit
Test that started failing on 20 July 2023

Another instance of this ICE appeared in my glibc bot on 20 July; compile
ibm1008_420.i with -O2. This failure was introduced by

commit ef28aadad6e5cff3d7494f3c97d435a6579a2e2d
Author: Jan Hubicka <jh@suse.cz>
Date:   Thu Jul 20 15:41:39 2023 +0200

    loop-ch improvements, part 3

although I fully expect it's really the same bug as for the other testcases
discussed here and it was just some perturbation to the processing of this test
that resulted in the appearance for that test with that commit.

  parent reply	other threads:[~2023-11-02 22:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-87281-4@http.gcc.gnu.org/bugzilla/>
2022-08-14 19:08 ` pinskia at gcc dot gnu.org
2022-08-14 19:58 ` slyfox at gcc dot gnu.org
2022-12-20 22:21 ` jbglaw@lug-owl.de
2023-06-24  9:45 ` jbglaw@lug-owl.de
2023-11-02 22:36 ` jsm28 at gcc dot gnu.org [this message]
2023-11-02 22:38 ` [Bug target/87281] [14 Regression] " jsm28 at gcc dot gnu.org
2024-01-10 10:12 ` rguenth at gcc dot gnu.org
2024-05-07  7:39 ` [Bug target/87281] [14/15 " rguenth 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-87281-4-zYyBqd13wh@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).