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 tree-optimization/55890] [4.7 Regression] calling a builtin func through a cast triggers an ICE Date: Mon, 04 Feb 2013 12:05:00 -0000 [thread overview] Message-ID: <bug-55890-4-oai1eFaIgU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55890-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55890 --- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> 2013-02-04 12:04:41 UTC --- Author: rguenth Date: Mon Feb 4 12:04:35 2013 New Revision: 195708 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=195708 Log: 2013-02-04 Richard Biener <rguenther@suse.de> Backport from mainline 2012-07-04 Richard Guenther <rguenther@suse.de> PR tree-optimization/53844 * tree-ssa-dse.c (dse_possible_dead_store_p): Properly handle the loop virtual PHI. * g++.dg/tree-ssa/pr53844.C: New testcase. 2012-12-13 Richard Biener <rguenther@suse.de> PR lto/55660 * tree-streamer.c (record_common_node): Check that we are not recursively pre-loading nodes we want to skip. Handle char_type_node appearing as part of va_list_type_node. * gcc.dg/lto/pr55660_0.c: New testcase. * gcc.dg/lto/pr55660_1.c: Likewise. 2013-02-04 Richard Biener <rguenther@suse.de> PR middle-end/55890 * gimple.h (gimple_call_builtin_class_p): New function. * gimple.c (validate_call): New function. (gimple_call_builtin_class_p): Likewise. * tree-ssa-structalias.c (find_func_aliases_for_builtin_call): Use gimple_call_builtin_class_p. (find_func_clobbers): Likewise. * tree-ssa-strlen.c (adjust_last_stmt): Likewise. (strlen_optimize_stmt): Likewise. * gcc.dg/torture/pr55890-1.c: New testcase. * gcc.dg/torture/pr55890-2.c: Likewise. Added: branches/gcc-4_7-branch/gcc/testsuite/g++.dg/tree-ssa/pr53844.C branches/gcc-4_7-branch/gcc/testsuite/gcc.dg/lto/pr55660_0.c branches/gcc-4_7-branch/gcc/testsuite/gcc.dg/lto/pr55660_1.c branches/gcc-4_7-branch/gcc/testsuite/gcc.dg/torture/pr55890-1.c branches/gcc-4_7-branch/gcc/testsuite/gcc.dg/torture/pr55890-2.c Modified: branches/gcc-4_7-branch/gcc/ChangeLog branches/gcc-4_7-branch/gcc/gimple.c branches/gcc-4_7-branch/gcc/gimple.h branches/gcc-4_7-branch/gcc/testsuite/ChangeLog branches/gcc-4_7-branch/gcc/tree-ssa-dse.c branches/gcc-4_7-branch/gcc/tree-ssa-strlen.c branches/gcc-4_7-branch/gcc/tree-ssa-structalias.c branches/gcc-4_7-branch/gcc/tree-streamer.c
next prev parent reply other threads:[~2013-02-04 12:05 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-06 21:22 [Bug c/55890] New: " vapier at gentoo dot org 2013-01-07 9:54 ` [Bug tree-optimization/55890] [4.7/4.8 Regression] " rguenth at gcc dot gnu.org 2013-01-07 10:03 ` rguenth at gcc dot gnu.org 2013-01-07 11:22 ` rguenth at gcc dot gnu.org 2013-01-07 12:07 ` rguenth at gcc dot gnu.org 2013-01-07 15:35 ` rguenth at gcc dot gnu.org 2013-01-07 15:36 ` [Bug tree-optimization/55890] [4.7 " rguenth at gcc dot gnu.org 2013-01-07 15:56 ` rguenth at gcc dot gnu.org 2013-01-08 8:39 ` jakub at gcc dot gnu.org 2013-01-11 23:40 ` vries at gcc dot gnu.org 2013-02-04 12:05 ` rguenth at gcc dot gnu.org [this message] 2013-02-04 12:08 ` rguenth at gcc dot gnu.org 2013-02-04 15:50 ` rguenth at gcc dot gnu.org 2013-02-04 15:51 ` 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-55890-4-oai1eFaIgU@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).