public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/52117] allocated arrays give incorrect results when used with RESHAPE in gcc v4.6.2
Date: Fri, 10 Feb 2012 20:45:00 -0000 [thread overview]
Message-ID: <bug-52117-4-pwmKz7sNzE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52117-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52117
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu.org
Severity|critical |normal
--- Comment #10 from kargl at gcc dot gnu.org 2012-02-10 20:44:47 UTC ---
(In reply to comment #9)
> Tobias
>
> We have a problem in v4.6.2 with the following (using the std=f95 flag):
> There seems to have been a limitation in past versions of gfortran with
> allocatable components inside derived types. It was supposed to have been
> fixed, and should be no more a compiler bug. It is valid (language-legal)
> fortran 95 and 2003, so must be a compiler limitation or compiler bug.
>
> Other compiles are fine as well (g95, ifort, etc.).
>
> Do you know if this has indeed been fixed?
The audit trail for this PR is quite confusing, and the above
is too vague to even guess at what your problem is.
next prev parent reply other threads:[~2012-02-10 20:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 20:32 [Bug fortran/52117] New: " sphirshman at yahoo dot com
2012-02-03 20:43 ` [Bug fortran/52117] " burnus at gcc dot gnu.org
2012-02-06 15:38 ` sphirshman at yahoo dot com
2012-02-06 17:47 ` burnus at gcc dot gnu.org
2012-02-06 19:47 ` sphirshman at yahoo dot com
2012-02-06 20:02 ` burnus at gcc dot gnu.org
2012-02-07 11:44 ` hirshmansp at ornl dot gov
2012-02-07 14:37 ` burnus at gcc dot gnu.org
2012-02-07 16:18 ` sphirshman at yahoo dot com
2012-02-10 20:01 ` sphirshman at yahoo dot com
2012-02-10 20:45 ` kargl at gcc dot gnu.org [this message]
2012-02-11 11:41 ` burnus at gcc dot gnu.org
2012-02-11 12:08 ` sphirshman at yahoo dot com
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-52117-4-pwmKz7sNzE@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).