public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/49394] [4.7 Regression] libstdc++-v3/testsuite/30_threads/lock_guard/cons/1.cc FAILs with -fipa-pta -fnon-call-exceptions Date: Tue, 14 Jun 2011 12:45:00 -0000 [thread overview] Message-ID: <bug-49394-4-VaSS6zqLCt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49394-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49394 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |4.7.0 --- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-06-14 12:45:43 UTC --- Maybe related to the g++.dg/torture/pr43879-1_1.C FAIL. Fix for that: Index: tree-ssa-structalias.c =================================================================== --- tree-ssa-structalias.c (revision 175011) +++ tree-ssa-structalias.c (working copy) @@ -3925,8 +3925,14 @@ handle_pure_call (gimple stmt, VEC(ce_s, static varinfo_t get_fi_for_callee (gimple call) { - tree decl, fn = gimple_call_fn (call); + tree decl, fn; + struct cgraph_edge *e; + e = cgraph_edge (cgraph_get_node (cfun->decl), call); + if (e && e->callee && e->callee->decl) + return get_vi_for_tree (e->callee->decl); + + fn = gimple_call_fn (call); if (fn && TREE_CODE (fn) == OBJ_TYPE_REF) fn = OBJ_TYPE_REF_EXPR (fn);
next prev parent reply other threads:[~2011-06-14 12:45 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-06-13 19:19 [Bug middle-end/49394] New: " zsojka at seznam dot cz 2011-06-14 12:45 ` rguenth at gcc dot gnu.org [this message] 2011-06-27 16:48 ` [Bug middle-end/49394] " rguenth at gcc dot gnu.org 2011-06-27 16:49 ` rguenth 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-49394-4-VaSS6zqLCt@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).