public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: Martin Sebor <msebor@gmail.com>,
	Thomas Schwinge <thomas@codesourcery.com>,
	 gcc-patches@gcc.gnu.org
Subject: Re: testsuite: Be more informative for ICEs
Date: Mon, 13 Dec 2021 14:12:26 -0500	[thread overview]
Message-ID: <fdd43e34a4a9c8e363328ae522407f9c52a7702e.camel@redhat.com> (raw)
In-Reply-To: <29c07bd3-de1b-4d10-7905-796d20bd1eec@gmail.com>

On Mon, 2021-12-13 at 10:53 -0700, Martin Sebor via Gcc-patches wrote:
> On 12/10/21 3:42 PM, Thomas Schwinge wrote:
> > Hi!
> > 
> > OK to push the attached "testsuite: Be more informative for ICEs"?
> 
> Adding more detail here seems like a useful improvement to me.
> 
> Martin

Agreed.  I don't think I can formally approve this patch, but it looks
like a big improvement to me, too.

Does it identify assertion failures, BTW?

Dave



  reply	other threads:[~2021-12-13 19:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-10 22:42 Thomas Schwinge
2021-12-13 17:53 ` Martin Sebor
2021-12-13 19:12   ` David Malcolm [this message]
2021-12-15 22:55     ` Thomas Schwinge
2021-12-14 22:58 ` Jeff Law

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=fdd43e34a4a9c8e363328ae522407f9c52a7702e.camel@redhat.com \
    --to=dmalcolm@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=msebor@gmail.com \
    --cc=thomas@codesourcery.com \
    /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).