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/47574] internal compiler error: in build2_stat, at tree.c:3795 Date: Tue, 01 Feb 2011 20:03:00 -0000 [thread overview] Message-ID: <bug-47574-4-N3yiSyhHC0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47574-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47574 --- Comment #4 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2011-02-01 18:32:44 UTC --- I cannot reproduce it on x86_64-apple-darwin10 with all the options/versions I have tried (including gcc version 4.6.0 20101106 (experimental) [trunk revision 166401]). One possibility could be a miscompilation due to gmp/mpfr/mpc: I use GMP version 5.0.1, MPFR version 3.0.0, MPC version 0.8.2 Do you know a minimal use of gdb?
next prev parent reply other threads:[~2011-02-01 20:03 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-02-01 16:17 [Bug fortran/47574] New: " mlosch@uni-bremen.de 2011-02-01 16:20 ` [Bug fortran/47574] " mlosch@uni-bremen.de 2011-02-01 16:54 ` burnus at gcc dot gnu.org 2011-02-01 18:06 ` mlosch@uni-bremen.de 2011-02-01 20:03 ` dominiq at lps dot ens.fr [this message] 2011-02-01 20:41 ` dominiq at lps dot ens.fr 2011-02-02 9:00 ` mlosch@uni-bremen.de 2011-02-02 9:09 ` mlosch@uni-bremen.de 2011-02-02 9:35 ` dominiq at lps dot ens.fr 2011-02-02 10:08 ` mlosch@uni-bremen.de 2011-02-02 10:28 ` mlosch@uni-bremen.de 2011-02-02 11:22 ` dominiq at lps dot ens.fr 2011-02-02 16:26 ` dominiq at lps dot ens.fr 2011-02-03 20:16 ` dominiq at lps dot ens.fr 2011-02-05 10:35 ` tkoenig at gcc dot gnu.org 2011-02-05 10:39 ` tkoenig 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-47574-4-N3yiSyhHC0@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).