public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug tree-optimization/49822] New: [gcc-4.7 regression] Segfault in remove_prop_source_from_use
@ 2011-07-23 14:06 rearnsha at gcc dot gnu.org
  2011-07-24 21:29 ` [Bug tree-optimization/49822] [4.7 " pinskia at gcc dot gnu.org
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: rearnsha at gcc dot gnu.org @ 2011-07-23 14:06 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49822

           Summary: [gcc-4.7 regression] Segfault in
                    remove_prop_source_from_use
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: rearnsha@gcc.gnu.org
            Target: arm-eabi


Created attachment 24815
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=24815
testcase

Attached testcase segfaults GCC for arm-eabi when compiled with

cc1 -marm -mcpu=arm7tdmi -Os -fno-short-enums

This was caused by:

2011-07-21  Richard Guenther  <rguenther@suse.de>

        * tree-ssa-forwprop.c (combine_conversions): Return whether
        we have to run cfg-cleanup.  Properly remove dead stmts.
        (ssa_forward_propagate_and_combine): Adjust.


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2011-07-26 11:04 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-07-23 14:06 [Bug tree-optimization/49822] New: [gcc-4.7 regression] Segfault in remove_prop_source_from_use rearnsha at gcc dot gnu.org
2011-07-24 21:29 ` [Bug tree-optimization/49822] [4.7 " pinskia at gcc dot gnu.org
2011-07-25 10:17 ` rguenth at gcc dot gnu.org
2011-07-25 14:15 ` rguenth at gcc dot gnu.org
2011-07-26 11:04 ` rearnsha at gcc dot gnu.org

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).