public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/107002] [13 Regression] ICE in column_range, at diagnostic-show-locus.cc:2236
Date: Thu, 22 Sep 2022 12:49:04 +0000 [thread overview]
Message-ID: <bug-107002-4-nqt3fuuxW9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107002-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107002
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2022-09-22
Status|UNCONFIRMED |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |dmalcolm at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Probably introduced by r13-2386-gbedfca647a9e9c1a, which added
-Wxor-used-as-pow.
Failing assertion in column_range's ctor:
2233 column_range (int start_, int finish_) : start (start_), finish
(finish_)
2234 {
2235 /* We must have either a range, or an insertion. */
2236 gcc_assert (start <= finish || finish == start - 1);
2237 }
where:
(gdb) p start_
$1 = 5
(gdb) p finish_
$2 = 0
next prev parent reply other threads:[~2022-09-22 12:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 17:36 [Bug c/107002] New: " gscfq@t-online.de
2022-09-22 6:48 ` [Bug c/107002] " rguenth at gcc dot gnu.org
2022-09-22 12:49 ` dmalcolm at gcc dot gnu.org [this message]
2022-09-22 19:25 ` [Bug c/107002] [13 Regression] ICE in column_range, at diagnostic-show-locus.cc:2236 since r13-2386-gbedfca647a9e9c1a marxin at gcc dot gnu.org
2022-10-18 8:42 ` rguenth at gcc dot gnu.org
2023-03-28 14:24 ` jakub at gcc dot gnu.org
2023-03-28 16:34 ` dmalcolm at gcc dot gnu.org
2023-03-28 18:36 ` cvs-commit at gcc dot gnu.org
2023-03-28 18:39 ` dmalcolm 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-107002-4-nqt3fuuxW9@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).