From: Sandra Loosemore <sandra@codesourcery.com>
To: <skpgkp2@gmail.com>, <gcc-patches@gcc.gnu.org>,
<gcc-regression@gcc.gnu.org>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Re: [r12-3321 Regression] FAIL: gfortran.dg/PR100914.f90 -Os (test for excess errors) on Linux/x86_64
Date: Thu, 2 Sep 2021 23:37:55 -0600 [thread overview]
Message-ID: <940f604d-c7e1-b829-263f-93e568c5c76d@codesourcery.com> (raw)
In-Reply-To: <20210903041859.DB2712864700@gskx-2.sc.intel.com>
On 9/2/21 10:18 PM, sunil.k.pandey wrote:
> On Linux/x86_64,
>
> 93b6b2f614eb692d1d8126ec6cb946984a9d01d7 is the first bad commit
> commit 93b6b2f614eb692d1d8126ec6cb946984a9d01d7
> Author: Sandra Loosemore <sandra@codesourcery.com>
> Date: Wed Aug 18 07:22:03 2021 -0700
>
> libgfortran: Further fixes for GFC/CFI descriptor conversions.
>
> caused
>
> FAIL: gfortran.dg/PR100914.f90 -O0 (test for excess errors)
> FAIL: gfortran.dg/PR100914.f90 -O1 (test for excess errors)
> FAIL: gfortran.dg/PR100914.f90 -O2 (test for excess errors)
> FAIL: gfortran.dg/PR100914.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess errors)
> FAIL: gfortran.dg/PR100914.f90 -O3 -g (test for excess errors)
> FAIL: gfortran.dg/PR100914.f90 -Os (test for excess errors)
I did not see this failure in my own testing, but I also had this patch
for another known bug in my stack:
https://gcc.gnu.org/pipermail/fortran/2021-August/056382.html
I just pinged that earlier this evening as it has not been reviewed yet.
I'll rebuild/retest without that patch and confirm that's what the
problem is.
-Sandra
next prev parent reply other threads:[~2021-09-03 5:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 4:18 sunil.k.pandey
2021-09-03 5:37 ` Sandra Loosemore [this message]
2021-09-03 17:24 ` Sandra Loosemore
2021-09-03 19:05 ` H.J. Lu
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=940f604d-c7e1-b829-263f-93e568c5c76d@codesourcery.com \
--to=sandra@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc-regression@gcc.gnu.org \
--cc=skpgkp2@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).