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/39519] [4.4 Regression] bad assignment to type with allocatable component
Date: Sun, 22 Mar 2009 12:22:00 -0000 [thread overview]
Message-ID: <20090322122224.20825.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39519-17482@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from pault at gcc dot gnu dot org 2009-03-22 12:22 -------
(In reply to comment #2)
> This PR should probably be marked as [4.3/4.4 Regression].
>
Dear, oh dear! This is annoying. The bug goes away if the first component of
the derived type is anything other than a pointer. Also, interchanging the
components clears the fault too. The derived type attribute alloc_comp is not
getting set for some reason, to judge by the code.
Paul
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39519
next prev parent reply other threads:[~2009-03-22 12:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-22 10:45 [Bug fortran/39519] New: " gilbert dot scott at easynet dot co dot uk
2009-03-22 10:53 ` [Bug fortran/39519] " dominiq at lps dot ens dot fr
2009-03-22 10:58 ` [Bug fortran/39519] [4,4 Regression] " steven at gcc dot gnu dot org
2009-03-22 11:14 ` [Bug fortran/39519] [4.4 " dominiq at lps dot ens dot fr
2009-03-22 12:22 ` pault at gcc dot gnu dot org [this message]
2009-03-22 17:54 ` pault at gcc dot gnu dot org
2009-03-22 18:26 ` hjl dot tools at gmail dot com
2009-03-22 21:17 ` steven at gcc dot gnu dot org
2009-03-31 16:00 ` [Bug fortran/39519] [4.3/4.4/4.5 " jsm28 at gcc dot gnu dot org
2009-03-31 19:44 ` jakub at gcc dot gnu dot org
2009-03-31 19:51 ` pault at gcc dot gnu dot org
2009-04-04 13:19 ` [Bug fortran/39519] [4.3/4.4 " pault at gcc dot gnu dot org
2009-04-04 14:47 ` pault at gcc dot gnu dot org
2009-04-04 14:50 ` 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=20090322122224.20825.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: 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).