public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/54120] [4.8 Regression] FAIL: gfortran.fortran-torture/execute/random_2.f90 execution Date: Mon, 30 Jul 2012 20:55:00 -0000 [thread overview] Message-ID: <bug-54120-4-anvtmEJub6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54120-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54120 John David Anglin <danglin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |steven at gcc dot gnu.org --- Comment #1 from John David Anglin <danglin at gcc dot gnu.org> 2012-07-30 20:55:42 UTC --- Introduced in 189366. Does this change affect recog_memoized?
next prev parent reply other threads:[~2012-07-30 20:55 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-29 17:46 [Bug fortran/54120] New: " danglin at gcc dot gnu.org 2012-07-30 20:55 ` danglin at gcc dot gnu.org [this message] 2012-07-31 14:50 ` [Bug middle-end/54120] " burnus at gcc dot gnu.org 2012-09-19 14:08 ` rguenth at gcc dot gnu.org 2012-12-19 10:55 ` jakub at gcc dot gnu.org 2012-12-19 12:58 ` dave.anglin at bell dot net 2012-12-22 23:01 ` danglin at gcc dot gnu.org 2012-12-22 23:02 ` danglin at gcc dot gnu.org 2012-12-22 23:07 ` jakub at gcc dot gnu.org 2012-12-22 23:35 ` danglin at gcc dot gnu.org 2012-12-22 23:38 ` danglin at gcc dot gnu.org 2013-01-07 14:51 ` jakub at gcc dot gnu.org 2013-01-07 16:34 ` jakub at gcc dot gnu.org 2013-01-07 17:28 ` jakub at gcc dot gnu.org 2013-01-07 18:09 ` dave.anglin at bell dot net 2013-01-08 8:34 ` jakub at gcc dot gnu.org 2013-01-08 9:09 ` jakub 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-54120-4-anvtmEJub6@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).