public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sphirshman at yahoo dot com" <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: Sat, 11 Feb 2012 12:08:00 -0000 [thread overview] Message-ID: <bug-52117-4-0ePetmbfai@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 --- Comment #12 from steven hirshman <sphirshman at yahoo dot com> 2012-02-11 12:08:02 UTC --- Thank you for your reply. I'll check with my coworker about that. From: burnus at gcc dot gnu.org <gcc-bugzilla@gcc.gnu.org> To: sphirshman@yahoo.com Sent: Saturday, February 11, 2012 6:40 AM Subject: [Bug fortran/52117] allocated arrays give incorrect results when used with RESHAPE in gcc v4.6.2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52117 --- Comment #11 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-02-11 11:40:36 UTC --- (In reply to comment #9) > 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. Allocatable components in derived types is not allowed in Fortran 95 - it has only been later added as Technical Report (TR) 15581 and it is part of Fortran 2003. Thus, the flag -std=f95 does not work if you need allocatable components. Hence, you have to choose one of the other options listed as comment #7: > Unless you provide me with a time machine [...] > The only solutions, I see, which do not require code changes are: > > - Use any GCC version before GCC 4.6.0; for instance GCC 4.5.x > - Use GCC 4.6 older than 2010-11-28 > - Use a GCC (any version) newer than 2012-02-03 > - Use -fno-realloc-lhs (caveat: Flag not supported before GCC 4.6) > - Use -std=f95 (caveat: Requires that the code compiles without error with > -std=f95) > > I personally would use -fno-realloc-lhs [...] > > For completeness, also the following code changes are possible; except for > the first one, they are not recommended: > > - Use an array spec for allocatable LHS, e.g. "B(:,:,:) = " > - Don't use allocatables left of " = RESHAPE" > - Make the expression on the RHS more complicated: add "+ 0" or surround with > "( )".
prev parent reply other threads:[~2012-02-11 12:08 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 2012-02-11 11:41 ` burnus at gcc dot gnu.org 2012-02-11 12:08 ` sphirshman at yahoo dot com [this message]
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-0ePetmbfai@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: 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).