public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/59534] [4.9 Regression] FAIL: libgomp.fortran/retval1.f90 execution test due to denormals Date: Tue, 17 Dec 2013 07:15:00 -0000 [thread overview] Message-ID: <bug-59534-4-Zy0W21R9Zz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59534-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59534 --- Comment #8 from Uroš Bizjak <ubizjak at gmail dot com> --- (In reply to Andrew Pinski from comment #6) > We are doing the correct thing for this testcase (the testcase should change > also) though most likely you can generate a testcase which short-circuits > the check. Let's ask a nice fortraner to fix the testcase then... > And then we should add a check for trapping of the comparisons. IEEE exception handling is not yet implemented, but alpha traps on denormals by default (that is how the problem was discovered). OTOH, if I add -mieee to the compile options, the exception on alpha goes away (as expected). >From gcc-bugs-return-437811-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 17 07:15:43 2013 Return-Path: <gcc-bugs-return-437811-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 20086 invoked by alias); 17 Dec 2013 07:15:43 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 19809 invoked by uid 48); 17 Dec 2013 07:15:38 -0000 From: "samsonov at google dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/59136] [4.9 Regression] llvm-symbolizer shouldn't be started always Date: Tue, 17 Dec 2013 07:15:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: samsonov at google dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-59136-4-KT4gl2Z3fx@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-59136-4@http.gcc.gnu.org/bugzilla/> References: <bug-59136-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-12/txt/msg01466.txt.bz2 Content-length: 268 http://gcc.gnu.org/bugzilla/show_bug.cgi?idY136 --- Comment #13 from Alexey Samsonov <samsonov at google dot com> --- I don't think fork() issue will be relevant here, at least for the minimalistic TSan test cases. Let's wait till we have libbacktrace symbolizer.
next prev parent reply other threads:[~2013-12-17 7:15 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-16 22:16 [Bug libgomp/59534] New: " ubizjak at gmail dot com 2013-12-16 22:21 ` [Bug libgomp/59534] " ubizjak at gmail dot com 2013-12-16 22:36 ` ubizjak at gmail dot com 2013-12-16 23:18 ` jakub at gcc dot gnu.org 2013-12-17 0:00 ` pinskia at gcc dot gnu.org 2013-12-17 0:24 ` pinskia at gcc dot gnu.org 2013-12-17 0:28 ` pinskia at gcc dot gnu.org 2013-12-17 7:15 ` ubizjak at gmail dot com [this message] 2013-12-17 14:38 ` [Bug testsuite/59534] " ubizjak at gmail dot com 2013-12-17 15:17 ` 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-59534-4-Zy0W21R9Zz@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).