public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Roman Lechtchinsky <rl@cs.tu-berlin.de>
To: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Getting rid of -g
Date: Wed, 12 Sep 2001 04:58:00 -0000	[thread overview]
Message-ID: <Pine.SOL.4.10.10109121352190.180-100000@sossusvlei> (raw)
In-Reply-To: <5.1.0.14.2.20010912134908.03016448@mail.lauterbach.com>

On Wed, 12 Sep 2001, Franz Sirl wrote:

> >the current release of the C compiler for the Cray T3E has a bug which
> >causes it to miscompile gcc if -g is specified. I'd like to turn this flag
> >off for building gcc on this platform but I'm somewhat confused about how
> >to do this. It doesn't really matter whether this flag is used when
> >building stage2 etc. but it shouldn't be passed to cc when building
> >stage1.
> 
> make bootstrap STAGE1_CFLAGS="-O0 -Wall -W"

Yes, but I want to fix configure/makefiles so that the user won't have to
worry about this.

Bye

Roman


  reply	other threads:[~2001-09-12  4:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-12  4:27 Roman Lechtchinsky
2001-09-12  4:50 ` Franz Sirl
2001-09-12  4:58   ` Roman Lechtchinsky [this message]
2001-09-12  5:41     ` Franz Sirl
2001-09-12  5:49       ` Roman Lechtchinsky
2001-09-12  6:09         ` Manfred Hollstein
2001-09-12  7:49           ` Roman Lechtchinsky
2001-09-12  8:44             ` Manfred Hollstein
2001-09-12  9:24               ` Roman Lechtchinsky
2001-09-12 10:06                 ` Richard Henderson
2001-09-12 10:24                   ` Roman Lechtchinsky
2001-09-12 10:49                     ` Richard Henderson
2001-09-13  1:08               ` Roman Lechtchinsky
2001-09-13  2:25                 ` Manfred Hollstein
2001-09-13  2:38                   ` Roman Lechtchinsky
2001-09-12  6:48         ` Andreas Schwab

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=Pine.SOL.4.10.10109121352190.180-100000@sossusvlei \
    --to=rl@cs.tu-berlin.de \
    --cc=Franz.Sirl-kernel@lauterbach.com \
    --cc=gcc@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).