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/99204] ICE in fold_read_from_constant_string, at fold-const.c:15441
Date: Mon, 22 Feb 2021 17:46:19 +0000 [thread overview]
Message-ID: <bug-99204-4-WHDc6vk7At@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99204-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99204
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
CC| |anlauf at gcc dot gnu.org
--- Comment #4 from anlauf at gcc dot gnu.org ---
(In reply to Dominique d'Humieres from comment #2)
> WORKSFORME:
>
> % gfc pr99204.f90
The issue really depends on optimization.
Confirmed for all tested -O greater than -O0: -Og, -O, -Os, -O2, -O3.
It disappears when declaring i volatile, as in
integer, volatile :: i = -12345678
next prev parent reply other threads:[~2021-02-22 17:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 16:56 [Bug fortran/99204] New: " gscfq@t-online.de
2021-02-22 16:57 ` [Bug fortran/99204] " gscfq@t-online.de
2021-02-22 17:02 ` dominiq at lps dot ens.fr
2021-02-22 17:19 ` gscfq@t-online.de
2021-02-22 17:46 ` anlauf at gcc dot gnu.org [this message]
2021-02-22 18:50 ` [Bug tree-optimization/99204] [8/9/10/11 Regression] " jakub at gcc dot gnu.org
2021-02-22 18:58 ` jakub at gcc dot gnu.org
2021-02-23 8:51 ` cvs-commit at gcc dot gnu.org
2021-02-23 9:12 ` [Bug tree-optimization/99204] [8/9/10 " jakub at gcc dot gnu.org
2021-03-19 23:29 ` cvs-commit at gcc dot gnu.org
2021-03-20 8:08 ` [Bug tree-optimization/99204] [8/9 " jakub at gcc dot gnu.org
2021-04-20 23:32 ` cvs-commit at gcc dot gnu.org
2021-04-22 16:51 ` cvs-commit at gcc dot gnu.org
2021-04-22 17:11 ` 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-99204-4-WHDc6vk7At@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).