From: Mike Stump <mikestump@comcast.net>
To: "Dominique d'Humières" <dominiq@lps.ens.fr>
Cc: fortran@gcc.gnu.org, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: RFA [Patch] PR 45076 - [OOP] gfortran.dg/dynamic_dispatch_6.f03 ICEs with -fprofile-use
Date: Fri, 11 Mar 2016 16:30:00 -0000 [thread overview]
Message-ID: <BF75374A-58EA-4BA0-A230-E0CC31F68D3D@comcast.net> (raw)
In-Reply-To: <A76CA122-A9BC-4059-B6B2-9A44EC9D7B05@lps.ens.fr>
On Mar 11, 2016, at 7:57 AM, Dominique d'Humières <dominiq@lps.ens.fr> wrote:
> AFAICT pr45076 is fixed on the gcc-4.9, gcc-5 branches, and trunk. I have borrowed the machinery in g++.dg/tree-prof/tree-prof.exp for the attached patch and tested it on the three branches. Is it OK as such or is there a better way to do the testing?
Ok. [ As always, anyone should feel free to chime in with suggestions, objections and improvements, if they know of any. ]
prev parent reply other threads:[~2016-03-11 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 15:57 Dominique d'Humières
2016-03-11 16:30 ` Mike Stump [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=BF75374A-58EA-4BA0-A230-E0CC31F68D3D@comcast.net \
--to=mikestump@comcast.net \
--cc=dominiq@lps.ens.fr \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
/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).