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/100724] -fwhole-program breaks module use
Date: Mon, 24 May 2021 19:59:04 +0000 [thread overview]
Message-ID: <bug-100724-4-e6eMfIAOcf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100724-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100724
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to fail| |10.3.1, 11.1.0, 12.0,
| |8.5.0, 9.3.1
Known to work| |9.2.0
--- Comment #3 from anlauf at gcc dot gnu.org ---
(In reply to Dave Love from comment #2)
> The manual says not to use -flto with -fwhole-program. Is that misleading?
I guess the manual entry has a reason, but I do not know why the optimimzations
implied by these options should not be combined.
> I checked self-built gfortran 10.2.0 again, and it definitely works for me
> without -flto on Debian 10, but it fails with Red Hat devtoolset's 10.2.1 on
> RHEL7. Odd...
I checked against gfortran 9.2.0, which works fine, whereas the current
development version 9.3.1 fails too.
The change likely happened in a newer developer version and was backported
to the release branches.
next prev parent reply other threads:[~2021-05-24 19:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 14:21 [Bug fortran/100724] New: " fx at gnu dot org
2021-05-23 19:19 ` [Bug fortran/100724] " anlauf at gcc dot gnu.org
2021-05-24 11:04 ` fx at gnu dot org
2021-05-24 19:59 ` anlauf at gcc dot gnu.org [this message]
2021-05-25 7:18 ` rguenth at gcc dot gnu.org
2021-05-25 10:48 ` fx at gnu dot org
2021-05-25 19:19 ` hubicka at ucw dot cz
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-100724-4-e6eMfIAOcf@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).