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/5830: The compiler crashes
Date: Tue, 12 Mar 2002 02:36:00 -0000	[thread overview]
Message-ID: <20020312103601.5728.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/5830; it has been noted by GNATS.

From: Gwenole Beauchesne <gbeauchesne@mandrakesoft.com>
To: Manuel Serrano <Manuel.Serrano@sophia.inria.fr>
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: Tue, 12 Mar 2002 11:27:47 +0100 (CET)

 Hi,
 
 > 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.
 
 You could:
 
 1) Build a gcc-3.0.4 with the patch I posted and try to rebuild your
 Scheme->C compiler. And tell us how it goes.
 
 2) Build your project with -fno-reorder-blocks added to your C[XX]FLAGS.
 
 Bye,
 Gwenole.
 


             reply	other threads:[~2002-03-12 10:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-12  2:36 Gwenole Beauchesne [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-15  0:06 Manuel Serrano
2002-03-10 23:46 Manuel Serrano
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=20020312103601.5728.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: link
Be 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).