public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/57987] Fortran finalizers considered extern-inline by middle-end Date: Fri, 26 Jul 2013 12:16:00 -0000 [thread overview] Message-ID: <bug-57987-4-5M7HEcjK7D@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57987-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57987 --- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> --- Comment on attachment 30558 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30558 An unsuccessful attempt to fix this >+ if (!has_coarray_vars || gfc_option.coarray == GFC_FCOARRAY_LIB) >+ (void) cgraph_create_node (fndecl); It seems to work if I change the condition to: || gfc_option.coarray != GFC_FCOARRAY_LIB) which matches the comment and looks more reasonable. (Don't ask me why the normal !(a && b != c) -> (!a || b == c) doesn't work. It's to hot to think about it.) >From gcc-bugs-return-426764-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jul 26 12:20:53 2013 Return-Path: <gcc-bugs-return-426764-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 4199 invoked by alias); 26 Jul 2013 12:20:53 -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 4113 invoked by uid 48); 26 Jul 2013 12:20:50 -0000 From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/57974] std::pow(std::complex<long double>(0),1) returns (-nan,-nan) Date: Fri, 26 Jul 2013 12:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: paolo.carlini at oracle dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-57974-4-b9JMNuHY26@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-57974-4@http.gcc.gnu.org/bugzilla/> References: <bug-57974-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-07/txt/msg01271.txt.bz2 Content-length: 485 http://gcc.gnu.org/bugzilla/show_bug.cgi?idW974 --- Comment #16 from Paolo Carlini <paolo.carlini at oracle dot com> --- Also, in practice, I think it's *very* hard to explain to the users why long double is so special, why the middle-end can't handle it in complete analogy with float and double. And since clang and icc are *already* doing it, apparently, you can't just tell them, vaguely, "it's very tough to implement" or "performance would be horrible" or something similar.
next prev parent reply other threads:[~2013-07-26 12:16 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-07-25 17:08 [Bug fortran/57987] New: " jamborm at gcc dot gnu.org 2013-07-26 12:00 ` [Bug fortran/57987] " jamborm at gcc dot gnu.org 2013-07-26 12:16 ` burnus at gcc dot gnu.org [this message] 2013-07-29 15:54 ` jamborm at gcc dot gnu.org 2013-07-30 12:12 ` hubicka at gcc dot gnu.org 2013-08-02 11:32 ` jamborm at gcc dot gnu.org 2013-08-06 12:50 ` jamborm 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-57987-4-5M7HEcjK7D@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).