From: Uros Bizjak <ubizjak@gmail.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Mikael Morin <mikael.morin@sfr.fr>,
Steve Kargl <sgk@troutmask.apl.washington.edu>,
Fortran List <fortran@gcc.gnu.org>
Subject: Re: *Ping* Re: [Patch, fortran] PR61831 side-effect deallocation of variable components
Date: Tue, 21 Jul 2015 09:32:00 -0000 [thread overview]
Message-ID: <CAFULd4ape_YHvSyBT7mPGNzQpDOa9+WrYYvtNu265Afh3EtBbQ@mail.gmail.com> (raw)
Hello!
> On Fri, Jul 10, 2015 at 06:35:30PM +0200, Mikael Morin wrote:
>> Ping: https://gcc.gnu.org/ml/fortran/2015-06/msg00075.html
>>
>
> Patch looks ok to me.
The new test introduced several testsuite failures, please see e.g. [1]:
UNRESOLVED: gfortran.dg/derived_constructor_comps_6.f90 -O0
scan-tree-dump-times original "__builtin_free" 33
UNRESOLVED: gfortran.dg/derived_constructor_comps_6.f90 -O0
scan-tree-dump-times original "__builtin_malloc" 15
UNRESOLVED: gfortran.dg/derived_constructor_comps_6.f90 -O1
scan-tree-dump-times original "__builtin_free" 33
UNRESOLVED: gfortran.dg/derived_constructor_comps_6.f90 -O1
scan-tree-dump-times original "__builtin_malloc" 15
UNRESOLVED: gfortran.dg/derived_constructor_comps_6.f90 -O2
scan-tree-dump-times original "__builtin_free" 33
UNRESOLVED: gfortran.dg/derived_constructor_comps_6.f90 -O2
scan-tree-dump-times original "__builtin_malloc" 15
UNRESOLVED: gfortran.dg/derived_constructor_comps_6.f90 -O3
-fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer
-finline-functions scan-tree-dump-times original "__builtin_free" 33
UNRESOLVED: gfortran.dg/derived_constructor_comps_6.f90 -O3
-fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer
-finline-functions scan-tree-dump-times original "__builtin_malloc"
15
UNRESOLVED: gfortran.dg/derived_constructor_comps_6.f90 -O3 -g
scan-tree-dump-times original "__builtin_free" 33
UNRESOLVED: gfortran.dg/derived_constructor_comps_6.f90 -O3 -g
scan-tree-dump-times original "__builtin_malloc" 15
UNRESOLVED: gfortran.dg/derived_constructor_comps_6.f90 -Os
scan-tree-dump-times original "__builtin_free" 33
UNRESOLVED: gfortran.dg/derived_constructor_comps_6.f90 -Os
scan-tree-dump-times original "__builtin_malloc" 15
(Also, the name of the test is not correctly stated in the ChangeLog entry).
Runtime tests can't scan their dumpfiles.
[1] https://gcc.gnu.org/ml/gcc-testresults/2015-07/msg02059.html
Uros.
next reply other threads:[~2015-07-21 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 9:32 Uros Bizjak [this message]
2015-07-21 12:47 ` [committed] fix PR61831 test (was: Re: *Ping* Re: [Patch, fortran] PR61831 side-effect deallocation of variable components) Mikael Morin
-- strict thread matches above, loose matches on Subject: below --
2015-07-21 10:09 *Ping* Re: [Patch, fortran] PR61831 side-effect deallocation of variable components Dominique d'Humières
2015-05-16 17:01 Mikael Morin
2015-06-21 13:01 ` Mikael Morin
2015-07-10 16:35 ` *Ping* " Mikael Morin
2015-07-16 22:35 ` Steve Kargl
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=CAFULd4ape_YHvSyBT7mPGNzQpDOa9+WrYYvtNu265Afh3EtBbQ@mail.gmail.com \
--to=ubizjak@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikael.morin@sfr.fr \
--cc=sgk@troutmask.apl.washington.edu \
/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).