public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Manuel Serrano <Manuel.Serrano@sophia.inria.fr> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/5830: The compiler crashes Date: Sun, 10 Mar 2002 23:46:00 -0000 [thread overview] Message-ID: <20020311074603.10703.qmail@sources.redhat.com> (raw) The following reply was made to PR c/5830; it has been noted by GNATS. From: Manuel Serrano <Manuel.Serrano@sophia.inria.fr> To: Gwenole Beauchesne <gbeauchesne@mandrakesoft.com> Cc: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, jh@suse.cz Subject: Re: c/5830: The compiler crashes Date: Mon, 11 Mar 2002 08:44:54 +0100 On Fri, 08 Mar 2002 19:29:30 +0100 Gwenole Beauchesne <gbeauchesne@mandrakesoft.com> wrote: > Hi, > > It doesn't appear to be fixed on the gcc-3.0-branch. On gcc-3.1-branch, > that appears to have been fixed with Jan's crossjumping patch of 2001/07/16: > <http://gcc.gnu.org/ml/gcc-patches/2001-07/msg01030.html> > > On 3.0-branch, gcc ICEs with the testcase of that PR and -O2 level. > However, it doesn't ICE with -O2 and -fno-reorder-blocks. > > With the following patch, derived from Jan's, 3.0-branch bootstrapped > and regtested OK. Note that if I make cleanup_cfg() after > reorder_basic_blocks() too, bootstrap fails. So I don't think that patch > is good enough. > > 2002-03-08 Gwenole Beauchesne <gbeauchesne@mandrakesoft.com> > > PR c/5830 > * toplev.c (rest_of_compilation): Do cleanup_cfg before > bb-reorder. [From Jan Hubicka for gcc-3.1, 2001/07/16] > > --- gcc-3.0.4/gcc/toplev.c.reorder-blocks Fri Mar 8 14:10:00 2002 > +++ gcc-3.0.4/gcc/toplev.c Fri Mar 8 15:45:46 2002 > @@ -3636,12 +3636,16 @@ > = optimize > 0 && only_leaf_regs_used () && leaf_function_p (); > #endif > > - if (optimize > 0 && flag_reorder_blocks) > + if (optimize > 0) > { > timevar_push (TV_REORDER_BLOCKS); > open_dump_file (DFI_bbro, decl); > - > - reorder_basic_blocks (); > + > + /* Last attempt to optimize CFG, as life analyzis possibly removed > + some instructions. */ > + cleanup_cfg (); > + if (flag_reorder_blocks) > + reorder_basic_blocks (); > > close_dump_file (DFI_bbro, print_rtl_with_bb, insns); > timevar_pop (TV_REORDER_BLOCKS); > > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5830 > I have seen the problem when compiling my Scheme->C compiler. This compiler is bootstrapped and it produces huge probably unusual C files. If you want me to test the whole compiler with a new version of GCC please, let me know. I you think that it could help, I could do this test for you. Sincerely, -- Manuel
next reply other threads:[~2002-03-11 7:46 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-10 23:46 Manuel Serrano [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-03-15 0:06 Manuel Serrano 2002-03-12 2:36 Gwenole Beauchesne 2002-03-08 10:36 Gwenole Beauchesne 2002-03-06 17:26 rodrigc 2002-03-04 8:46 Zack Weinberg 2002-03-04 7:56 Manuel.Serrano
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=20020311074603.10703.qmail@sources.redhat.com \ --to=manuel.serrano@sophia.inria.fr \ --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).