public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/54871] [4.8 regression] gfortran.dg/vector_subscript_1.f90 FAILs Date: Fri, 12 Oct 2012 08:41:00 -0000 [thread overview] Message-ID: <bug-54871-4-OV3HWXEvij@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54871-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54871 --- Comment #2 from Rainer Orth <ro at gcc dot gnu.org> 2012-10-12 08:41:06 UTC --- Created attachment 28430 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28430 bad assembler output
next prev parent reply other threads:[~2012-10-12 8:41 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-09 9:39 [Bug fortran/54871] New: " ro at gcc dot gnu.org 2012-10-09 9:40 ` [Bug fortran/54871] " ro at gcc dot gnu.org 2012-10-12 8:40 ` ro at gcc dot gnu.org 2012-10-12 8:41 ` ro at gcc dot gnu.org [this message] 2012-10-12 9:33 ` ebotcazou at gcc dot gnu.org 2012-10-12 21:37 ` ebotcazou at gcc dot gnu.org 2012-10-13 20:22 ` [Bug rtl-optimization/54871] " ebotcazou at gcc dot gnu.org 2012-10-13 20:30 ` ebotcazou 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-54871-4-OV3HWXEvij@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).