From: Marek Polacek <polacek@redhat.com>
To: Nathan Sidwell <nathan@acm.org>
Cc: Marek Polacek via Gcc-patches <gcc-patches@gcc.gnu.org>,
richard.sandiford@arm.com
Subject: Re: RFC: Monitoring old PRs, new dg directives
Date: Mon, 10 Aug 2020 17:36:57 -0400 [thread overview]
Message-ID: <20200810213657.GF1314761@redhat.com> (raw)
In-Reply-To: <e8af4c4f-1b18-49a1-8058-8ca0cf23090e@acm.org>
On Mon, Aug 10, 2020 at 08:58:54AM -0400, Nathan Sidwell wrote:
> On 8/10/20 4:48 AM, Richard Sandiford wrote:
> > Marek Polacek via Gcc-patches <gcc-patches@gcc.gnu.org> writes:
> > > > > > sure.
> > > > > > * develop patch
> > > > > > * run testsuite
> > > > > > * observe unexpected ICEs
> > > > > > * load g++.log into editor
> > > > > > * ^sinternal comp
> > > > > > * gets to first unexpected ICE
> > > > > > * debug it.
> > > > > >
> > > > > > What does '^sinternal comp' become? As there could be many expected ICEs
> > > > > > it'll be painful to determine whether any particular utterance of 'internal
> > > > > > compiler' is expected or not.
> > > > >
> > > > > That is a problem I don't know how to deal with. I know how to pass
> > > > > additional options to the compiler from dejagnu. I thought maybe I could use
> > > > > -pass-exit-codes, redirect stderr to /dev/null, and check if the exit code is
> > > > > ICE_EXIT_CODE, but there seems to be no way to do that redirection. So I'm
> > > > > stuck.
> > > > >
> > > > > Though, you could just grep for '^FAIL.*internal comp', which will find the
> > > > > first unexpected ICE. Contrary to the expected ICEs, the unexpected ICEs will
> > > > > be shown in 'Excess errors:'. Won't that work?
> > > >
> > > > Read what I wrote:
> > > > > > * load g++.log into editor
> > > > > > * ^sinternal comp
> > > >
> > > > are you telling me not to use an editor for this task? the search is so one
> > > > can get the command line. Grepping the log file will not do that.
> > >
> > > No, I'm saying that looking for '^FAIL.*internal comp' (in an editor) instead
> > > of just 'internal comp' will get you to the ICEs you care about. In vim,
> > > '/^FAIL.*in' gets me there.
> >
> > Yeah, this works. I'm not sure whether Nathan's ^s is isearch
> > or regexp-isearch :-)
>
> It was incremental :) it;s kind of nice just to stop typing when it hits the
> first ICE message! But, I'm not going to object any more, I guess I'll live
> with it. </grumpy old man>
Sorry.
> [I'm sure I can figure out some emacs macro binding to DTRT]
I'm sure you could. If it becomes painful, I could also add
GCC_TESTSUITE_SKIP_ICE_TESTS (disabled by default) or similar to skip dg-ice
tests.
Marek
next prev parent reply other threads:[~2020-08-10 21:37 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 21:44 Marek Polacek
2020-07-29 1:37 ` Mike Stump
2020-08-04 21:34 ` Marek Polacek
2020-07-29 3:02 ` Jeff Law
2020-08-04 21:37 ` Marek Polacek
2020-07-29 8:40 ` Richard Sandiford
2020-08-04 21:47 ` Marek Polacek
2020-08-04 22:33 ` Mike Stump
2020-08-05 0:54 ` Marek Polacek
2020-08-05 15:03 ` Nathan Sidwell
2020-08-05 23:29 ` Marek Polacek
2020-08-06 14:01 ` Nathan Sidwell
2020-08-06 22:55 ` Marek Polacek
2020-08-07 13:21 ` Nathan Sidwell
2020-08-07 14:18 ` Marek Polacek
2020-08-10 8:48 ` Richard Sandiford
2020-08-10 12:58 ` Nathan Sidwell
2020-08-10 21:36 ` Marek Polacek [this message]
2020-08-10 21:30 ` RFC: Monitoring old PRs, new dg directives [v2] Marek Polacek
2020-08-10 22:58 ` Mike Stump
2020-11-10 14:15 ` Thomas Schwinge
2020-11-10 19:07 ` Marek Polacek
2020-08-07 0:01 ` RFC: Monitoring old PRs, new dg directives Mike Stump
2020-08-07 13:16 ` Nathan Sidwell
2020-08-10 22:35 ` Mike Stump
2020-08-05 19:59 ` Marek Polacek
2020-08-05 20:01 ` Mike Stump
2020-08-06 12:27 ` Marek Polacek
2020-08-06 12:30 ` Jakub Jelinek
2020-08-06 12:36 ` Marek Polacek
2020-08-05 8:04 ` Richard Sandiford
2020-08-05 12:59 ` Marek Polacek
2020-07-29 20:37 ` Jason Merrill
2020-08-04 22:08 ` Marek Polacek
2020-08-04 22:45 ` Mike Stump
2020-08-05 12:56 ` Marek Polacek
2020-08-05 19:44 ` Mike Stump
2020-07-29 22:00 ` Martin Sebor
2020-08-04 22:16 ` Marek Polacek
2020-08-04 22:53 ` Mike Stump
2020-08-05 0:59 ` Marek Polacek
2020-07-30 9:08 ` Martin Liška
2020-08-04 22:22 ` Marek Polacek
2020-08-10 3:04 ` Martin Liška
2020-07-30 9:54 ` Jakub Jelinek
2020-08-04 22:33 ` Marek Polacek
2020-08-05 7:58 ` Richard Sandiford
2020-08-05 13:18 ` Marek Polacek
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=20200810213657.GF1314761@redhat.com \
--to=polacek@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nathan@acm.org \
--cc=richard.sandiford@arm.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).