public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/95537] [11 regression] gfortran.dg/pr95090.f90 since r11-670
Date: Thu, 04 Jun 2020 21:21:26 +0000 [thread overview]
Message-ID: <bug-95537-4-ddWu96WpK9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95537-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95537
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot gnu.org
--- Comment #6 from anlauf at gcc dot gnu.org ---
(In reply to Bill Seurer from comment #5)
> Still fails:
>
> make -k check-gcc-fortran RUNTESTFLAGS=dg.exp=gfortran.dg/pr95090.f90
>
> FAIL: gfortran.dg/pr95090.f90 -O (internal compiler error)
> FAIL: gfortran.dg/pr95090.f90 -O (test for excess errors)
It turns out that this PR and PR95530 are unrelated issues regarding
buffer overflow in different places.
Can you add the patch in this PR, comment#4, and in PR95530 comment#6?
I've "regtested" on x86_64-pc-linux-gnu, but this might miss further
buffer overflows elsewhere.
next prev parent reply other threads:[~2020-06-04 21:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 16:32 [Bug fortran/95537] New: " seurer at linux dot vnet.ibm.com
2020-06-04 16:33 ` [Bug fortran/95537] " seurer at linux dot vnet.ibm.com
2020-06-04 17:24 ` anlauf at gcc dot gnu.org
2020-06-04 20:19 ` seurer at linux dot vnet.ibm.com
2020-06-04 20:55 ` anlauf at gcc dot gnu.org
2020-06-04 21:13 ` seurer at linux dot vnet.ibm.com
2020-06-04 21:21 ` anlauf at gcc dot gnu.org [this message]
2020-06-04 21:24 ` seurer at linux dot vnet.ibm.com
2020-06-04 22:29 ` seurer at linux dot vnet.ibm.com
2020-06-05 6:30 ` rguenth at gcc dot gnu.org
2020-06-05 18:30 ` cvs-commit at gcc dot gnu.org
2020-06-05 19:32 ` cvs-commit at gcc dot gnu.org
2020-06-05 20:35 ` cvs-commit at gcc dot gnu.org
2020-06-05 20:38 ` anlauf 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-95537-4-ddWu96WpK9@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).