public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/108125] Suggestion for improving bug-box / reporting on ICE
Date: Thu, 11 May 2023 15:47:33 +0000	[thread overview]
Message-ID: <bug-108125-4-vpAa0d5SZO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108125-4@http.gcc.gnu.org/bugzilla/>

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

Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ebotcazou at gcc dot gnu.org
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #2 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> The ice for Ada front end already provides this information. Even saying
> what to attachments are required.

Right, including the chain of instances for the source location.

> What more improvements are needed to compared to what clang does?
> Outputting internal state is hard to do really and confuse everyone.

I agree, and neither a backtrace nor a snapshot of data structures are
sufficient to diagnose the problem in most cases, the compiler is much too
complex for this.

      parent reply	other threads:[~2023-05-11 15:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 11:23 [Bug ada/108125] New: " jesper.quorning at gmail dot com
2022-12-15 11:40 ` [Bug ada/108125] " pinskia at gcc dot gnu.org
2023-05-11 15:47 ` ebotcazou at gcc dot gnu.org [this message]

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-108125-4-vpAa0d5SZO@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).