public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Gwenole Beauchesne <gbeauchesne@mandrakesoft.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/5250: ICE in print_rtl_and_abort, at flow.c:6458 with -O3 Date: Fri, 08 Feb 2002 12:46:00 -0000 [thread overview] Message-ID: <20020208204602.25725.qmail@sources.redhat.com> (raw) The following reply was made to PR c/5250; it has been noted by GNATS. From: Gwenole Beauchesne <gbeauchesne@mandrakesoft.com> To: dmuell@gmx.net, gerold.jury@utanet.at, joel@gcc.gnu.org, maciej@imsa.edu, utx@penguin.cz, relf@os2.ru, snowwolf@one2one-networks.com, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, nottelm@uni-muenster.de Cc: Subject: Re: c/5250: ICE in print_rtl_and_abort, at flow.c:6458 with -O3 Date: Fri, 08 Feb 2002 23:09:39 +0100 Hi, PR c/4257, PR c/5409, PR c/5250 appear to have been fixed in gcc-3.1 when Jan Hubicka killed jump_optimize: <http://gcc.gnu.org/ml/gcc-patches/2001-07/msg01430.html> . I don't know if I get it right but the following patch attempts to disable the NOOP_MOVES jump_optimization prior to register renaming. 2002-02-08 Gwenole Beauchesne <gbeauchesne@mandrakesoft.com> PR c/4257, PR c/5049, PR c/5250 * toplev.c (rest_of_compilation): Don't perform NOOP_MOVES jump_optimization prior to register renaming. However, tidy the CFG by deleting unreachable code. * gcc.c-torture/compile/20020208-1.c: New test. --- gcc-3.0.4/gcc/testsuite/gcc.c-torture/compile/20020208-1.c.no-noop_moves Fri Feb 8 20:28:37 2002 +++ gcc-3.0.4/gcc/testsuite/gcc.c-torture/compile/20020208-1.c Fri Feb 8 20:28:37 2002 @@ -0,0 +1,11 @@ +/* Origin: PR c/4257 from Volker Reichelt <reichelt@igpm.rwth-aachen.de>. */ +/* This testcase caused gcc-3.0.1 to ICE if compiled with -O1 + -frename-registers. */ + +void f () +{ + unsigned int *p; + p++; + *p += *p / (*p < 2); +} + --- gcc-3.0.4/gcc/toplev.c.no-noop_moves Fri Feb 8 20:01:51 2002 +++ gcc-3.0.4/gcc/toplev.c Fri Feb 8 20:01:51 2002 @@ -3546,9 +3546,8 @@ timevar_push (TV_FLOW2); open_dump_file (DFI_flow2, decl); - jump_optimize (insns, !JUMP_CROSS_JUMP, - JUMP_NOOP_MOVES, !JUMP_AFTER_REGSCAN); find_basic_blocks (insns, max_reg_num (), rtl_dump_file); + cleanup_cfg (); /* On some machines, the prologue and epilogue code, or parts thereof, can be represented as RTL. Doing so lets us schedule insns between http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5250
next reply other threads:[~2002-02-08 20:46 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-02-08 12:46 Gwenole Beauchesne [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-03-03 18:17 rodrigc 2002-03-03 18:06 Craig Rodrigues 2002-01-02 12:38 rodrigc 2002-01-02 10:06 nottelm
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=20020208204602.25725.qmail@sources.redhat.com \ --to=gbeauchesne@mandrakesoft.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).