public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub 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 since r13-2386-gbedfca647a9e9c1a
Date: Tue, 28 Mar 2023 14:24:48 +0000	[thread overview]
Message-ID: <bug-107002-4-lodaxsAew0@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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
David, any progress here?
Should the diagnostic callers be more careful when passing multiple fixit
locations to make sure they don't overlap (I think in this case they are even
the exact same location), or should diagnostic-show-locus.cc recover from it?
Given the same location for both, they are equal:
(gdb) p last_correction->m_affected_bytes
$34 = {start = 1, finish = 4}
(gdb) p affected_bytes
$35 = {start = 1, finish = 4}
and so trying to create a column range for finish + 1 of the former to start -
1
of the latter is invalid.

  parent reply	other threads:[~2023-03-28 14:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21 17:36 [Bug c/107002] New: [13 Regression] ICE in column_range, at diagnostic-show-locus.cc:2236 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
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 [this message]
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-lodaxsAew0@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).