public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pault at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/29216] Derived type components of function results are not initialised Date: Sun, 08 Oct 2006 22:04:00 -0000 [thread overview] Message-ID: <20061008220356.17395.qmail@sourceware.org> (raw) In-Reply-To: <bug-29216-13292@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from pault at gcc dot gnu dot org 2006-10-08 22:03 ------- Created an attachment (id=12397) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12397&action=view) Preliminary fix for this PR This has only been tested against the reporter's example. Regtesting and checking against other case (eg. arrays or characters) will follow in the next couple of days. Paul -- pault at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |pault at gcc dot gnu dot org |dot org | Status|NEW |ASSIGNED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29216
next prev parent reply other threads:[~2006-10-08 22:04 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-09-25 15:47 [Bug fortran/29216] New: " stephan dot kramer at imperial dot ac dot uk 2006-09-25 16:29 ` [Bug fortran/29216] " pault at gcc dot gnu dot org 2006-10-08 22:04 ` pault at gcc dot gnu dot org [this message] 2006-10-10 7:56 ` fxcoudert at gcc dot gnu dot org 2006-10-10 12:48 ` pault at gcc dot gnu dot org 2006-10-10 20:49 ` pault at gcc dot gnu dot org 2006-10-16 16:51 ` pault at gcc dot gnu dot org 2006-10-17 4:55 ` pault at gcc dot gnu dot org 2006-10-17 14:05 ` patchapp at dberlin dot org 2006-10-18 11:20 ` patchapp at dberlin dot org 2006-10-19 4:51 ` pault at gcc dot gnu dot org 2006-10-19 6:42 ` pault at gcc dot gnu dot org 2006-11-10 21:53 ` pault 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=20061008220356.17395.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).