public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mikael Morin <morin-mikael@orange.fr>
To: Harald Anlauf <anlauf@gmx.de>, Jerry D <jvdelisle2@gmail.com>
Cc: Manfred Schwarb <manfred99@gmx.ch>, fortran <fortran@gcc.gnu.org>
Subject: Re: Aw: Re: Invalid "dg-do run" in the testsuite (with 2 blanks)
Date: Tue, 26 Mar 2024 09:53:27 +0100	[thread overview]
Message-ID: <68de82ad-b9a1-48cb-b52e-b282515afb87@orange.fr> (raw)
In-Reply-To: <trinity-e5a4f440-e78b-4e88-812a-1949b0d6221e-1711405814261@3c-app-gmx-bap03>

Le 25/03/2024 à 23:30, Harald Anlauf a écrit :
>> On 3/25/24 12:53 PM, Harald Anlauf wrote:
>>>>>>>
(...)
>>>>>>
>>>>>> One failure after fixing all the spaces ( sed is our friend ).
>>>>>>
>>>>>> FAIL: gfortran.dg/inline_matmul_1.f90   -O0   scan-tree-dump-times optimized "_gfortran_matmul" 0
>>>
>>> This does actually point to an issue with the testcase:
>>> it only works properly with optimization enabled.
>>>
>>> Manual inspection of this test and the expected dump suggests
>>> that e.g. -O1 could have been added to the dg-options directive.
>>>
>>> Shouldn't we fix at least the dg-options of that testcase?
>>>
For what it's worth, the scan-tree-dump-times directive can be 
conditionalized on target __OPTIMIZE__, so that it's active with 
optimization and inactive with -O0.  This would make the test pass 
regardless of compiler flags.
Of course if the goal is lowering the test execution time, it wouldn't help.

(...)
> 
> I find it somewhat unsatisfactory though, to have a behavior of the
> testsuite harness that is so intranparent.
> 
Agreed.




  parent reply	other threads:[~2024-03-26  8:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-24 20:19 Harald Anlauf
2024-03-24 23:26 ` Jerry D
2024-03-25  4:53 ` Jerry D
2024-03-25  8:27   ` Manfred Schwarb
2024-03-25 17:38     ` Jerry D
2024-03-25 19:53       ` Harald Anlauf
2024-03-25 20:52         ` Jerry D
2024-03-25 22:30           ` Aw: " Harald Anlauf
2024-03-26  1:24             ` Jerry D
2024-03-26  7:49               ` Richard Biener
2024-03-26  8:53             ` Mikael Morin [this message]
2024-04-02  6:46 ` Andrew Pinski
2024-04-02 17:44   ` Jerry D

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=68de82ad-b9a1-48cb-b52e-b282515afb87@orange.fr \
    --to=morin-mikael@orange.fr \
    --cc=anlauf@gmx.de \
    --cc=fortran@gcc.gnu.org \
    --cc=jvdelisle2@gmail.com \
    --cc=manfred99@gmx.ch \
    /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).