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/48031] [4.4 Regression] gcc.c-torture/compile/pr42956.c ICEs gcc on m68k-linux, ivopts related? Date: Mon, 18 Apr 2011 14:55:00 -0000 [thread overview] Message-ID: <bug-48031-4-A5olmXDsZg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48031-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48031 --- Comment #21 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-04-18 14:37:18 UTC --- Author: rguenth Date: Mon Apr 18 14:37:08 2011 New Revision: 172652 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=172652 Log: 2011-04-18 Richard Guenther <rguenther@suse.de> Backported from 4.6 branch 2011-03-11 Jakub Jelinek <jakub@redhat.com> PR c++/48035 * init.c (build_zero_init_1): Extracted from build_zero_init. Add FIELD_SIZE argument, if non-NULL and field bit_position as not smaller than that, don't add that field's initializer. Pass DECL_SIZE as last argument to build_zero_init_1 for DECL_FIELD_IS_BASE fields. (build_zero_init): Use build_zero_init_1. * g++.dg/inherit/virtual8.C: New test. 2011-03-05 Zdenek Dvorak <ook@ucw.cz> PR rtl-optimization/47899 * cfgloopmanip.c (fix_bb_placements): Fix first argument to flow_loop_nested_p when moving the loop upward. * gcc.dg/pr47899.c: New test. 2011-03-15 Richard Guenther <rguenther@suse.de> PR middle-end/48031 * fold-const.c (fold_indirect_ref_1): Do not create new variable-sized or variable-indexed array accesses when in gimple form. Added: branches/gcc-4_5-branch/gcc/testsuite/g++.dg/inherit/virtual8.C branches/gcc-4_5-branch/gcc/testsuite/gcc.dg/pr47899.c
next prev parent reply other threads:[~2011-04-18 14:55 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-08 10:01 [Bug target/48031] New: [4,4, 4.5 regression] " mikpe at it dot uu.se 2011-03-08 11:02 ` [Bug tree-optimization/48031] [4.4/4.5 Regression] " rguenth at gcc dot gnu.org 2011-03-08 14:23 ` mikpe at it dot uu.se 2011-03-08 21:40 ` mikpe at it dot uu.se 2011-03-09 9:22 ` rguenther at suse dot de 2011-03-09 23:37 ` mikpe at it dot uu.se 2011-03-10 9:22 ` mikpe at it dot uu.se 2011-03-10 9:34 ` rguenther at suse dot de 2011-03-10 11:03 ` rguenth at gcc dot gnu.org 2011-03-10 12:35 ` ebotcazou at gcc dot gnu.org 2011-03-10 12:36 ` rguenther at suse dot de 2011-03-10 12:46 ` ebotcazou at gcc dot gnu.org 2011-03-10 12:58 ` rguenther at suse dot de 2011-03-10 13:04 ` ebotcazou at gcc dot gnu.org 2011-03-10 13:07 ` rguenther at suse dot de 2011-03-10 13:10 ` rguenth at gcc dot gnu.org 2011-03-10 14:03 ` mikpe at it dot uu.se 2011-03-15 8:53 ` mikpe at it dot uu.se 2011-03-15 10:06 ` rguenth at gcc dot gnu.org 2011-03-28 10:22 ` rguenth at gcc dot gnu.org 2011-04-10 10:38 ` rguenth at gcc dot gnu.org 2011-04-16 11:18 ` jakub at gcc dot gnu.org 2011-04-18 14:15 ` [Bug tree-optimization/48031] [4.4 " rguenth at gcc dot gnu.org 2011-04-18 14:42 ` [Bug tree-optimization/48031] [4.4/4.5 " rguenth at gcc dot gnu.org 2011-04-18 14:55 ` rguenth at gcc dot gnu.org [this message] 2012-03-13 16:57 ` [Bug tree-optimization/48031] [4.4 " 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-48031-4-A5olmXDsZg@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).