From: Tobias Burnus <burnus@net-b.de>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: gcc-patches@gcc.gnu.org, Fortran List <fortran@gcc.gnu.org>
Subject: Re: [PATCH, testsuite]: Fix scan string of gfortran.dg/intrinsic_size_3.f90
Date: Wed, 09 Jan 2013 19:29:00 -0000 [thread overview]
Message-ID: <50EDC518.7020602@net-b.de> (raw)
In-Reply-To: <CAFULd4bxyQig00bBS7Z+ef4hP1O3k0jLUxTvsv9063hL4Er2Jw@mail.gmail.com>
The patch is OK. Thanks!
Tobias
Uros Bizjak wrote:
> The regexp in the scan string assumes that dumped temporaries have
> exactly 4 numbers. Sometimes, this is not the case.
>
> Attached patch fixes scan string to match a number with arbitrary
> number of places instead.
>
> 2012-01-09 Uros Bizjak <ubizjak@gmail.com>
>
> * gfortran.dg/intrinsic_size_3.f90: Make scan-tree-dump-times
> number matching more robust.
>
> Tested on x86_64-pc-linux-gnu and alphaev68-linux-gnu, where it fixes
> spurious test failure.
>
> OK for mainline?
prev parent reply other threads:[~2013-01-09 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 19:15 Uros Bizjak
2013-01-09 19:29 ` Tobias Burnus [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=50EDC518.7020602@net-b.de \
--to=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=ubizjak@gmail.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).