public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "stefan.mauerberger at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/55932] New: DDT's default structure constructor does not work with having allocatable member variables Date: Thu, 10 Jan 2013 07:59:00 -0000 [thread overview] Message-ID: <bug-55932-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55932 Bug #: 55932 Summary: DDT's default structure constructor does not work with having allocatable member variables Classification: Unclassified Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: stefan.mauerberger@gmail.com Created attachment 29138 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29138 minimal working example Hi Everybody! First of all, this is my first bug-report. In case I am doing something inappropriate pleas be soft with me. Concerning my problem: Invoking the default DDT structure constructor on types with allocatable member variables causes an internal compiler error. I tried with 4.7.1, 4.7.2 and 4.8.0 20121008. Defining a DDT having an allocatable member variable TYPE :: test_typ REAL, ALLOCATABLE :: a END TYPE the default structure constructor causes gfortran to crash my_test_typ = test_typ(a=1.0) As far as I can see, my code is valid Fortran. With NAG, PGI and Intel everything works just fine. If you need more details pleas let me know. Cheers, Stefan Environment: Ubuntu 12.10 How-To-Repeat: Try to compile the attached code
next reply other threads:[~2013-01-10 7:59 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-10 7:59 stefan.mauerberger at gmail dot com [this message] 2013-01-10 10:38 ` [Bug fortran/55932] " dominiq at lps dot ens.fr 2013-01-11 11:50 ` stefan.mauerberger at gmail dot com 2014-01-05 17:40 ` [Bug fortran/55932] [F03] ICE for structure constructor with scalar allocatable component janus at gcc dot gnu.org 2014-01-05 17:51 ` janus at gcc dot gnu.org 2014-01-05 18:42 ` janus at gcc dot gnu.org 2014-01-09 20:39 ` janus at gcc dot gnu.org 2014-01-09 21:49 ` janus at gcc dot gnu.org 2014-01-10 14:10 ` janus at gcc dot gnu.org 2014-01-10 14:13 ` janus at gcc dot gnu.org 2015-04-17 12:34 ` dominiq at lps dot ens.fr
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-55932-4@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: linkBe 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).