public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/44945] [4.6 Regression] Wrong decl for module vars / FAIL: gfortran.dg/char_array_structure_constructor.f90 Date: Fri, 16 Jul 2010 14:47:00 -0000 [thread overview] Message-ID: <20100716144706.1106.qmail@sourceware.org> (raw) In-Reply-To: <bug-44945-12313@http.gcc.gnu.org/bugzilla/> ------- Comment #18 from burnus at gcc dot gnu dot org 2010-07-16 14:47 ------- Answer: With the patch, one gets: gfortran -fwhole-file gfortran.dg/default_initialization_4.f90 without the patch (and still -fwhole-file) it works. The reason is that one does not "copy" over the backend_decl for the components - which one might need to do recursively as the components might again be derived types. Thus, it fails at trans-expr.c's gfc_conv_component_ref for: gcc_assert (c->backend_decl). Actually, I do not quite understand why BT_CLASS works - the BT_DERIVED check of comment 13 should be also false for BT_CLASS, which means its backend_decl should already be imported with -fwhole-file. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44945
next prev parent reply other threads:[~2010-07-16 14:47 UTC|newest] Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-07-15 8:32 [Bug middle-end/44945] New: [4.6 Regression] " dominiq at lps dot ens dot fr 2010-07-15 8:39 ` [Bug middle-end/44945] " rguenth at gcc dot gnu dot org 2010-07-15 14:38 ` [Bug fortran/44945] " burnus at gcc dot gnu dot org 2010-07-15 15:23 ` dominiq at lps dot ens dot fr 2010-07-15 15:24 ` dominiq at lps dot ens dot fr 2010-07-15 15:27 ` dominiq at lps dot ens dot fr 2010-07-15 16:02 ` [Bug middle-end/44945] " burnus at gcc dot gnu dot org 2010-07-15 16:25 ` dominiq at lps dot ens dot fr 2010-07-15 18:56 ` dominiq at lps dot ens dot fr 2010-07-15 20:20 ` jakub at gcc dot gnu dot org 2010-07-16 8:39 ` [Bug fortran/44945] " rguenth at gcc dot gnu dot org 2010-07-16 8:51 ` dominiq at lps dot ens dot fr 2010-07-16 9:12 ` [Bug fortran/44945] [4.6 Regression] Wrong decl for module vars / " burnus at gcc dot gnu dot org 2010-07-16 10:08 ` jakub at gcc dot gnu dot org 2010-07-16 12:08 ` burnus at gcc dot gnu dot org 2010-07-16 12:09 ` burnus at gcc dot gnu dot org 2010-07-16 12:33 ` jakub at gcc dot gnu dot org 2010-07-16 14:22 ` burnus at gcc dot gnu dot org 2010-07-16 14:38 ` paul dot richard dot thomas at gmail dot com 2010-07-16 14:47 ` burnus at gcc dot gnu dot org [this message] 2010-07-23 20:13 ` burnus at gcc dot gnu dot org 2010-07-23 20:16 ` burnus at gcc dot gnu dot org 2010-07-24 5:38 ` dominiq at lps dot ens dot fr 2010-07-24 6:52 ` burnus at gcc dot gnu dot org 2010-07-24 7:50 ` dominiq at lps dot ens dot fr 2010-07-24 13:44 ` rguenther at suse dot de 2010-07-24 18:14 ` burnus at gcc dot gnu dot org 2010-07-28 7:41 ` burnus at gcc dot gnu dot org 2010-08-17 9:42 ` pault at gcc dot gnu dot org 2010-08-18 14:41 ` mikael at gcc dot gnu dot org 2010-09-21 13:16 ` rguenth at gcc dot gnu dot org [not found] <bug-44945-4@http.gcc.gnu.org/bugzilla/> 2011-02-19 12:27 ` pault at gcc dot gnu.org 2011-02-19 13:46 ` dominiq at lps dot ens.fr 2011-02-19 13:55 ` burnus at gcc dot gnu.org 2011-02-19 15:12 ` paul.richard.thomas at gmail dot com 2011-02-20 16:28 ` pault at gcc dot gnu.org 2011-02-20 16:37 ` pault 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=20100716144706.1106.qmail@sourceware.org \ --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).