public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/60370] TRANSPOSE on rhs of allocatable array assignment gives error with -fcheck=bounds Date: Sat, 01 Mar 2014 19:23:00 -0000 [thread overview] Message-ID: <bug-60370-4-h4aQ26Q4Tc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60370-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60370 --- Comment #4 from Mikael Morin <mikael at gcc dot gnu.org> --- Created attachment 32239 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32239&action=edit Tentative patch moving realloc code before bound checking This patch doesn't work, so it may not be a code ordering issue after all.
next prev parent reply other threads:[~2014-03-01 19:23 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-28 20:05 [Bug fortran/60370] New: TRANSPOSE on rhs of allocatable array assignment gives bounds error townsend at astro dot wisc.edu 2014-03-01 13:39 ` [Bug fortran/60370] TRANSPOSE on rhs of allocatable array assignment gives error with -fcheck=bounds janus at gcc dot gnu.org 2014-03-01 16:00 ` anlauf at gmx dot de 2014-03-01 18:16 ` mikael at gcc dot gnu.org 2014-03-01 19:23 ` mikael at gcc dot gnu.org [this message] 2014-03-03 12:47 ` janus at gcc dot gnu.org 2014-03-03 21:40 ` mikael at gcc dot gnu.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-60370-4-h4aQ26Q4Tc@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).