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/97009] [9/10/11 Regression] Inlining with non-standard selected_int_kind leads to errors
Date: Thu, 10 Sep 2020 18:57:48 +0000 [thread overview]
Message-ID: <bug-97009-4-FTem5PhVe7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97009-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97009
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.4
Ever confirmed|0 |1
Known to fail| |11.0
Summary|Inlining with non-standard |[9/10/11 Regression]
|selected_int_kind leads to |Inlining with non-standard
|errors |selected_int_kind leads to
| |errors
Keywords| |wrong-code
Last reconfirmed| |2020-09-10
Status|UNCONFIRMED |NEW
Known to work| |8.4.1
Priority|P3 |P4
--- Comment #2 from anlauf at gcc dot gnu.org ---
It appears to be a combination of inlining and optimizations that are present
at -O2 but not at -O1.
OK:
gfc-11 pr97009.f90 -O1 -finline
gfc-11 pr97009.f90 -O2 -fno-inline
Not OK:
gfc-11 pr97009.f90 -O2 -finline
The output in the latter case appears to be random junk.
But valgrind does not show anything for me, nor does ASAN.
Could also be some ME issue.
next prev parent reply other threads:[~2020-09-10 18:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 11:32 [Bug fortran/97009] New: " pvitt at posteo dot de
2020-09-10 11:33 ` [Bug fortran/97009] " pvitt at posteo dot de
2020-09-10 18:57 ` anlauf at gcc dot gnu.org [this message]
2020-09-10 20:20 ` [Bug tree-optimization/97009] [9/10/11 Regression] " anlauf at gcc dot gnu.org
2020-09-11 18:17 ` anlauf at gcc dot gnu.org
2020-10-12 12:10 ` rguenth at gcc dot gnu.org
2021-03-31 20:26 ` jamborm at gcc dot gnu.org
2021-03-31 20:28 ` jamborm at gcc dot gnu.org
2021-03-31 21:32 ` jamborm at gcc dot gnu.org
2021-04-01 8:12 ` cvs-commit at gcc dot gnu.org
2021-04-01 9:51 ` cvs-commit at gcc dot gnu.org
2021-04-01 13:38 ` [Bug tree-optimization/97009] [9 " jamborm at gcc dot gnu.org
2021-04-08 16:58 ` cvs-commit at gcc dot gnu.org
2021-04-08 16:58 ` jamborm at gcc dot gnu.org
2024-03-27 5:00 ` pinskia 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-97009-4-FTem5PhVe7@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).