public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andre Vehreschild <vehre@gmx.de>
To: Mikael Morin <mikael.morin@sfr.fr>
Cc: Dominique Dhumieres <dominiq@lps.ens.fr>,
	fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, Fortran] PR fortran/60414 fix ICE was: PR 60414: Patch proposal
Date: Tue, 26 Aug 2014 09:30:00 -0000	[thread overview]
Message-ID: <20140826113012.77851d12@vepi2.private> (raw)
In-Reply-To: <53F0A8BA.2000303@sfr.fr>

Hi,

On Sun, 17 Aug 2014 15:06:02 +0200
Mikael Morin <mikael.morin@sfr.fr> wrote:

> Le 17/08/2014 14:26, Dominique Dhumieres a écrit :
> > As Mikael said in https://gcc.gnu.org/ml/fortran/2014-08/msg00047.html
> > 
> >> the testcase should check that the code generated is actually working,
> >> not just that the ICE disappeared. ...
> > 
> Well, this is for another patch where deferred character variable are
> made acceptable as argument to unlimited polymorphic dummies.
> Here the ICE comes (if I remember correctly) from the wrong generic
> procedure being picked, so there is not really some new feature enabled
> with the patch.

This is correct so far. 

> 
> > thus I think the test should be run, i.e., '! { dg-do compile }' should
> > be replaced with '! { dg-do run }' (I have checked that the test succeeds).
> > 
> I don't have a strong opinion for it, but I'm OK with that change.
> In fact the initial test was a run one, and it has been changed to
> compile.  Andre: why?

I was asked to move to compile only, because a run test takes a lot of time.
I was told that the run test compiles the code multiple times with different
optimization. This issue was deemed to be solely on the compile stage and was
not influenced by optimization. Therefore I agreed to switch to dg-do compile.
That the test is fine for running, too, is merely for my training of how to do
that. My opinion is, that dg-do compile is sufficient to prove, that PR60414 is
resolved, because that is the sole purpose of the patch. I understand
Dominique wanting to have the dg-do run, because the effectiveness of the patch
is only shown on running the test. Is there a compromise of running a test, but
only for one optimization stage? Then may be we can do that.

- Andre
-- 
Andre Vehreschild * Email: vehre ad gmx dot de 

  reply	other threads:[~2014-08-26  9:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140721072605.0D680105@mailhost.lps.ens.fr>
     [not found] ` <20140721150350.10b35dd3@vepi2.private>
2014-07-21 15:47   ` Dominique d'Humières
2014-07-26 20:14     ` Mikael Morin
2014-08-06 19:23       ` [PATCH, Fortran] PR fortran/60414 fix ICE was: " Andre Vehreschild
2014-08-17 11:42         ` Mikael Morin
2014-08-17 12:26           ` Dominique Dhumieres
2014-08-17 13:06             ` Mikael Morin
2014-08-26  9:30               ` Andre Vehreschild [this message]
2014-12-03 17:08                 ` Andre Vehreschild
2014-12-03 17:13                   ` Dominique d'Humières
2014-12-03 21:49                   ` FX
2014-12-05 14:29 Dominique Dhumieres

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=20140826113012.77851d12@vepi2.private \
    --to=vehre@gmx.de \
    --cc=dominiq@lps.ens.fr \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mikael.morin@sfr.fr \
    /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).