public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/67740] Wrong association status of allocatable character pointer in derived types
Date: Sat, 10 Oct 2015 10:05:00 -0000 [thread overview]
Message-ID: <bug-67740-4-JJxZJal1vX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67740-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67740
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2015-10-10
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Confirmed with 5.2 and 6.0. I get the following ICE with 4.9
pr67740.f90:20:0: internal compiler error: in gimplify_expr, at gimplify.c:8538
allocate(character(4) :: myBase%string)
the change occurred between revisions r221423 (2015-03-13, ICE) and
r2214164+patches (2015-03-16, compiles).
next prev parent reply other threads:[~2015-10-10 10:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 6:59 [Bug fortran/67740] New: " baradi09 at gmail dot com
2015-10-10 10:05 ` dominiq at lps dot ens.fr [this message]
2021-05-03 12:51 ` [Bug fortran/67740] " bardeau at iram dot fr
2023-09-26 19:57 ` anlauf at gcc dot gnu.org
2023-09-26 20:28 ` anlauf at gcc dot gnu.org
2023-09-27 20:07 ` anlauf at gcc dot gnu.org
2023-10-08 8:44 ` pault at gcc dot gnu.org
2023-10-08 20:43 ` anlauf at gcc dot gnu.org
2023-10-09 20:29 ` anlauf at gcc dot gnu.org
2023-10-12 6:27 ` cvs-commit at gcc dot gnu.org
2023-10-26 9:36 ` cvs-commit at gcc dot gnu.org
2023-10-26 9:39 ` pault at gcc dot gnu.org
2023-10-26 12:08 ` baradi09 at gmail dot com
2024-05-14 20:06 ` 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-67740-4-JJxZJal1vX@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).