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 c++/115599] ICE: qsort checking failed during GIMPLE pass: reassoc (error: qsort comparator non-negative on sorted output: 150142972) Date: Sun, 23 Jun 2024 12:37:31 +0000 [thread overview] Message-ID: <bug-115599-4-oJpJJkRovK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115599-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115599 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2024-06-23 Keywords| |ice-checking, | |missed-optimization Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- It's compare_repeat_factors (gdb) p (*repeat_factor_vec.m_vec)[0] $6 = (repeat_factor &) @0x5d6a7b8: {factor = <ssa_name 0x7ffff3396a20 36814>, rank = 2147549184, count = 1, repr = <tree 0x0>} (gdb) p (*repeat_factor_vec.m_vec)[4] $7 = (repeat_factor &) @0x5d6a838: {factor = <ssa_name 0x7ffff33db8b8 15299>, rank = 1, count = 1, repr = <tree 0x0>} where one obvious issue might be that rank is unsigned (and count is int64). I'm testing a fix. Note this bug only results in less optimal code.
next prev parent reply other threads:[~2024-06-23 12:37 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-23 11:54 [Bug c++/115599] New: " iamanonymous.cs at gmail dot com 2024-06-23 12:37 ` rguenth at gcc dot gnu.org [this message] 2024-06-23 12:43 ` [Bug tree-optimization/115599] " rguenth at gcc dot gnu.org 2024-06-23 12:48 ` sjames at gcc dot gnu.org 2024-06-23 12:50 ` sjames at gcc dot gnu.org 2024-06-24 7:28 ` cvs-commit at gcc dot gnu.org 2024-06-24 7:29 ` 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-115599-4-oJpJJkRovK@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).