public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/62251] [5 Regression] FAIL: gfortran.dg/quad_2.f90 execution test Date: Tue, 17 Feb 2015 19:22:00 -0000 [thread overview] Message-ID: <bug-62251-4-3FkmdMSuKV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-62251-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62251 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Last reconfirmed| |2015-02-17 CC| |jakub at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Yes, can you please debug this? Try e.g. GCC 5 compiled testcase against 4.9 libgfortran or vice versa, if the difference is in the binaries, do side-by-side debugging of the 4.9 and 5 version in the debugger and watch where things differ, if it is on the library side, identify which call differs?
next prev parent reply other threads:[~2015-02-17 19:22 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-24 16:40 [Bug target/62251] New: [5.0 " danglin at gcc dot gnu.org 2014-11-19 13:30 ` [Bug target/62251] " rguenth at gcc dot gnu.org 2014-12-02 1:36 ` [Bug target/62251] [5 " danglin at gcc dot gnu.org 2015-02-02 14:41 ` burnus at gcc dot gnu.org 2015-02-02 14:41 ` burnus at gcc dot gnu.org 2015-02-17 19:22 ` jakub at gcc dot gnu.org [this message] 2015-02-19 14:35 ` jakub at gcc dot gnu.org 2015-02-20 19:09 ` [Bug target/62251] " danglin at gcc dot gnu.org 2015-02-21 18:57 ` dave.anglin at bell dot net 2015-02-24 15:41 ` dave.anglin at bell dot net 2015-03-08 23:02 ` danglin 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-62251-4-3FkmdMSuKV@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).