public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/84345] [10/11/12/13 Regression] ICE: qsort checking failed (error: qsort comparator non-negative on sorted output: 1)
Date: Thu, 19 Jan 2023 14:10:22 +0000	[thread overview]
Message-ID: <bug-84345-4-XqbTjZmgPw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-84345-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #19 from Richard Biener <rguenth at gcc dot gnu.org> ---
As to comment#7 I agree, for some qsort comparators we probably do not care if
the outcome is really sorted in the end and the issue with different qsort
implementations producing differently sorted results is gone.

Maybe for those we should have a separately named entry, skipping the
verification?

gcc_heuristic_sort_nocheck ()?

  parent reply	other threads:[~2023-01-19 14:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-84345-4@http.gcc.gnu.org/bugzilla/>
2021-05-14  9:49 ` [Bug rtl-optimization/84345] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01  8:10 ` rguenth at gcc dot gnu.org
2021-09-20 10:43 ` pinskia at gcc dot gnu.org
2021-12-28 10:43 ` pinskia at gcc dot gnu.org
2021-12-28 10:43 ` pinskia at gcc dot gnu.org
2022-05-27  9:38 ` [Bug rtl-optimization/84345] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:34 ` jakub at gcc dot gnu.org
2022-12-20 13:16 ` jbglaw@lug-owl.de
2022-12-20 16:57 ` pinskia at gcc dot gnu.org
2023-01-19 14:10 ` rguenth at gcc dot gnu.org [this message]
2023-07-07 10:33 ` [Bug rtl-optimization/84345] [11/12/13/14 " 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-84345-4-XqbTjZmgPw@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).