public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/64613] <incomplete type> allocatable array after 4.7 Date: Sun, 30 Aug 2015 14:42:00 -0000 [thread overview] Message-ID: <bug-64613-4-zI7h1f9rAP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64613-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64613 Dominique d'Humieres <dominiq at lps dot ens.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution|--- |FIXED --- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> --- > Actually the problem was because I recompiled vanilla versions of GCC/GDB > on Fedora (I was on Fedora 17 with GCC 4.7). Fedora has long history > of patches for GBD include VLA. After trying serveral times with Archer > and other VLA implement, I gave up. The best way I can suggest > to a normal user is grabbing a new version of Fedora with recent version > of GCC and GDB... Oldest supported version is now 4.9. If the problem persists with Fedora, please report upstream. > Unfortunately, if one is on OS X, I can't find any solution atm. I don't understand this reference to OS X.
prev parent reply other threads:[~2015-08-30 14:42 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-15 13:24 [Bug fortran/64613] New: " ql.le at hotmail dot com 2015-03-31 11:22 ` [Bug fortran/64613] " dominiq at lps dot ens.fr 2015-03-31 12:25 ` ql.le at hotmail dot com 2015-08-30 14:42 ` dominiq at lps dot ens.fr [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-64613-4-zI7h1f9rAP@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).