public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu.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: Sun, 20 Feb 2011 16:28:00 -0000 [thread overview]
Message-ID: <bug-44945-4-vQewszrztY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-44945-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44945
--- Comment #33 from Paul Thomas <pault at gcc dot gnu.org> 2011-02-20 16:23:57 UTC ---
Author: pault
Date: Sun Feb 20 16:23:50 2011
New Revision: 170337
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=170337
Log:
2011-02-20 Paul Thomas <pault@gcc.gnu.org>
PR fortran/45077
PR fortran/44945
* trans-types.c (gfc_get_derived_type): Remove code that looks
for decls in gsym and add call to gfc_get_module_backend_decl.
* trans.h : Add prototype for gfc_get_module_backend_decl.
* trans-decl.c (gfc_get_module_backend_decl): New function.
(gfc_get_symbol_decl): Call it.
2011-02-20 Paul Thomas <pault@gcc.gnu.org>
PR fortran/45077
PR fortran/44945
* gfortran.dg/whole_file_28.f90 : New test.
* gfortran.dg/whole_file_29.f90 : New test.
Added:
trunk/gcc/testsuite/gfortran.dg/whole_file_28.f90
trunk/gcc/testsuite/gfortran.dg/whole_file_29.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/trans-decl.c
trunk/gcc/fortran/trans-types.c
trunk/gcc/fortran/trans.h
trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2011-02-20 16:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2011-02-20 16:37 ` pault at gcc dot gnu.org
2010-07-15 8:32 [Bug middle-end/44945] New: [4.6 Regression] " 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
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
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-44945-4-vQewszrztY@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).