public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/106079] [12/13 regression] gfortran.dg/boz_15.f90 fails after r12-6498-g07c60b8e33
Date: Sat, 30 Jul 2022 02:49:43 +0000 [thread overview]
Message-ID: <bug-106079-4-nuAGlbMQlx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106079-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106079
--- Comment #4 from seurer at gcc dot gnu.org ---
The patch causes a bunch of new failures:
FAIL: gfortran.dg/c-interop/allocatable-dummy.f90 -Os execution test
FAIL: gfortran.dg/c-interop/allocate-errors.f90 -O0 execution test
FAIL: gfortran.dg/c-interop/argument-association-assumed-rank-7.f90 -O1
execution test
FAIL: gfortran.dg/c-interop/argument-association-assumed-rank-7.f90 -O2
execution test
FAIL: gfortran.dg/c-interop/cf-descriptor-3.f90 -O2 execution test
FAIL: gfortran.dg/c-interop/cf-descriptor-7.f90 -Os execution test
FAIL: gfortran.dg/c-interop/contiguous-3.f90 -O0 execution test
Though it did fix these:
FAIL: gfortran.dg/c-interop/fc-descriptor-6.f90 -O1 execution test
FAIL: gfortran.dg/boz_15.f90 -O0 execution test
FAIL: gfortran.dg/boz_15.f90 -O1 execution test
FAIL: gfortran.dg/boz_15.f90 -O2 execution test
FAIL: gfortran.dg/boz_15.f90 -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions execution test
FAIL: gfortran.dg/boz_15.f90 -O3 -g execution test
FAIL: gfortran.dg/boz_15.f90 -Os execution test
next prev parent reply other threads:[~2022-07-30 2:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 12:24 [Bug libfortran/106079] New: [12/13 regression] gfortran.dg/boz_15.f90 fails after gcc-12-6498-g07c60b8e33 seurer at gcc dot gnu.org
2022-06-24 12:53 ` [Bug libfortran/106079] " rguenth at gcc dot gnu.org
2022-07-25 15:52 ` [Bug libfortran/106079] [12/13 regression] gfortran.dg/boz_15.f90 fails after r12-6498-g07c60b8e33 rguenth at gcc dot gnu.org
2022-07-29 14:35 ` jakub at gcc dot gnu.org
2022-07-29 20:58 ` seurer at gcc dot gnu.org
2022-07-30 2:49 ` seurer at gcc dot gnu.org [this message]
2022-07-30 10:46 ` jakub at gcc dot gnu.org
2022-07-30 11:19 ` jakub at gcc dot gnu.org
2022-08-01 6:26 ` cvs-commit at gcc dot gnu.org
2022-08-01 22:07 ` seurer at gcc dot gnu.org
2022-08-03 9:22 ` cvs-commit at gcc dot gnu.org
2022-08-03 9:24 ` jakub at gcc dot gnu.org
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=bug-106079-4-nuAGlbMQlx@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).