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/50890] [4.7 Regression] ICE in fold_convert_loc, at fold-const.c:1894 Date: Wed, 02 Nov 2011 08:46:00 -0000 [thread overview] Message-ID: <bug-50890-4-FTHpzyPB8d@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50890-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50890 --- Comment #3 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-11-02 08:46:12 UTC --- Author: rguenth Date: Wed Nov 2 08:46:08 2011 New Revision: 180763 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=180763 Log: 2010-11-02 Richard Guenther <rguenther@suse.de> PR tree-optimization/50890 * gimple.h (gimple_fold_call): Remove. * gimple-fold.c (fold_stmt_1): Move all call related code to ... (gimple_fold_call): ... here. Make static. Update the cannot-inline flag on direct calls. * ipa-inline.c (early_inliner): Copy the cannot-inline flag from the statements to the edges. * gcc.dg/torture/pr50890.c: New testcase. Added: trunk/gcc/testsuite/gcc.dg/torture/pr50890.c Modified: trunk/gcc/ChangeLog trunk/gcc/gimple-fold.c trunk/gcc/gimple.h trunk/gcc/ipa-inline.c trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2011-11-02 8:46 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-27 21:54 [Bug middle-end/50890] New: " belyshev at depni dot sinp.msu.ru 2011-10-28 9:45 ` [Bug middle-end/50890] " rguenth at gcc dot gnu.org 2011-10-28 12:45 ` rguenth at gcc dot gnu.org 2011-11-02 8:46 ` rguenth at gcc dot gnu.org [this message] 2011-11-02 8:48 ` rguenth at gcc dot gnu.org 2011-11-03 19:18 ` ebotcazou 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-50890-4-FTHpzyPB8d@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).