public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/34884] [4.3 Regression] gfortran.dg/array_constructor_9.f90 Date: Sun, 20 Jan 2008 16:35:00 -0000 [thread overview] Message-ID: <20080120155729.12436.qmail@sourceware.org> (raw) In-Reply-To: <bug-34884-682@http.gcc.gnu.org/bugzilla/> ------- Comment #13 from hjl dot tools at gmail dot com 2008-01-20 15:57 ------- It happens for me on Linux/Intel64 with -m32: http://gcc.gnu.org/ml/gcc-testresults/2008-01/msg00907.html My configuration is configure flags: --enable-clocale=gnu --with-system-zlib --enable-decimal-float=bid --with-demangler-in-ld --enable-shared --enable-threads=posix --enable-haifa --enable-checking=assert --prefix=/usr/gcc-4.3 --with-local-prefix=/usr/local -- hjl dot tools at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- Component|middle-end |fortran Target Milestone|4.3.0 |--- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34884
next prev parent reply other threads:[~2008-01-20 15:58 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-01-20 8:45 [Bug fortran/34884] New: " hjl dot tools at gmail dot com 2008-01-20 11:31 ` [Bug fortran/34884] " dominiq at lps dot ens dot fr 2008-01-20 12:05 ` dominiq at lps dot ens dot fr 2008-01-20 12:22 ` dominiq at lps dot ens dot fr 2008-01-20 13:20 ` dominiq at lps dot ens dot fr 2008-01-20 13:54 ` [Bug middle-end/34884] " pinskia at gcc dot gnu dot org 2008-01-20 13:54 ` dominiq at lps dot ens dot fr 2008-01-20 15:17 ` zadeck at naturalbridge dot com 2008-01-20 15:22 ` dominiq at lps dot ens dot fr 2008-01-20 15:35 ` zadeck at naturalbridge dot com 2008-01-20 15:40 ` dominiq at lps dot ens dot fr 2008-01-20 16:07 ` zadeck at naturalbridge dot com 2008-01-20 16:29 ` dominiq at lps dot ens dot fr 2008-01-20 16:31 ` zadeck at naturalbridge dot com 2008-01-20 16:35 ` hjl dot tools at gmail dot com [this message] 2008-01-20 19:39 ` [Bug fortran/34884] " zadeck at naturalbridge dot com 2008-01-20 22:29 ` [Bug middle-end/34884] " pinskia at gcc dot gnu dot org 2008-01-21 0:05 ` zadeck at naturalbridge dot com 2008-01-21 0:13 ` steven at gcc dot gnu dot org 2008-01-21 0:28 ` zadeck at naturalbridge dot com 2008-01-21 9:08 ` bonzini at gnu dot org 2008-01-21 13:23 ` zadeck at naturalbridge dot com 2008-01-21 13:42 ` bonzini at gnu dot org 2008-01-21 13:55 ` zadeck at naturalbridge dot com 2008-01-21 14:44 ` stevenb dot gcc at gmail dot com 2008-01-21 14:55 ` steven at gcc dot gnu dot org 2008-01-21 14:55 ` dominiq at lps dot ens dot fr 2008-01-21 15:15 ` bonzini at gnu dot org 2008-01-21 15:15 ` rguenth at gcc dot gnu dot org 2008-01-21 15:43 ` zadeck at naturalbridge dot com 2008-01-21 16:44 ` jsm28 at gcc dot gnu dot org 2008-01-22 13:50 ` zadeck at naturalbridge dot com 2008-01-22 14:04 ` zadeck at gcc dot gnu dot org 2008-01-22 14:13 ` zadeck at naturalbridge dot com 2008-01-22 14:47 ` zadeck at naturalbridge 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=20080120155729.12436.qmail@sourceware.org \ --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).