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/66366] ICE on invalid with non-allocatable CLASS variable [OOP]
Date: Wed, 03 Jun 2015 13:46:00 -0000 [thread overview]
Message-ID: <bug-66366-4-kSNiTJKYDG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66366-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66366
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |error-recovery,
| |ice-on-invalid-code
Status|UNCONFIRMED |NEW
Last reconfirmed| |2015-06-03
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
With gfortran 4.5.4 I get
pr66366.f90:9.27:
class(t1d) :: transfer
1
Error: Component 'transfer' with CLASS at (1) must be allocatable or pointer
twice, from 4.6 to 4.8, I get a segmentation fault, and from 4.9 to trunk 6.0,
I get the ICE after the error.
next prev parent reply other threads:[~2015-06-03 13:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 19:19 [Bug fortran/66366] New: " abensonca at gmail dot com
2015-06-03 13:46 ` dominiq at lps dot ens.fr [this message]
2015-06-22 22:54 ` [Bug fortran/66366] " abensonca at gmail dot com
2015-06-22 22:58 ` abensonca at gmail dot com
2021-01-08 20:37 ` [Bug fortran/66366] [OOP] ICE on invalid with non-allocatable CLASS variable anlauf at gcc dot gnu.org
2021-01-08 20:43 ` anlauf at gcc dot gnu.org
2021-05-14 10:02 ` 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-66366-4-kSNiTJKYDG@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).