public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mikael Morin <mikael.morin@sfr.fr>
To: Andre Vehreschild <vehre@gmx.de>
Cc: GCC-Patches-ML <gcc-patches@gcc.gnu.org>,
	GCC-Fortran-ML	<fortran@gcc.gnu.org>
Subject: Re: [Patch, Fortran] Prevent segfault with dump-*-original for implicit class expressions.
Date: Tue, 28 Apr 2015 12:06:00 -0000	[thread overview]
Message-ID: <553F77A5.8070708@sfr.fr> (raw)
In-Reply-To: <20150428124337.79d3f638@gmx.de>

Hello,

Le 28/04/2015 12:43, Andre Vehreschild a écrit :
> To get the testsuite accepting a dump-fortran-original, I had to insert a
> dg-prune-output. Without the prune output, dejagnu was reporting excess errors.
> The prune removes all output after the first Namespace: that starts the
> fortran-dump. I am not that happy with it, because ICEs in the dump will not be
> detected that way. But I could not find a better solution yet. Does anyone know
> of a better way to solve this? Best would be to have the fortran dump go to a
> file like all other dumps, but that is not scope of this patch.
> 
Without a better idea, the scope of the dg-prune-output should be
limited at least.
As the dump ends with a "-------" line, you can use the
"Namespace:.*-{42}" regular expression.
OK with that change.  Thanks.

Mikael

  reply	other threads:[~2015-04-28 12:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13 10:33 Andre Vehreschild
2015-04-24  8:32 ` [Ping, Patch, " Andre Vehreschild
2015-04-25 21:13 ` [Patch, " Mikael Morin
2015-04-28 10:59   ` Andre Vehreschild
2015-04-28 12:06     ` Mikael Morin [this message]
2015-04-28 19:43       ` [commited, Patch, " Andre Vehreschild

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=553F77A5.8070708@sfr.fr \
    --to=mikael.morin@sfr.fr \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=vehre@gmx.de \
    /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).