public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sdack at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/30853] warnings about traditional.c during bootstrap with -O3, leading to internal error
Date: Fri, 23 Feb 2007 15:53:00 -0000	[thread overview]
Message-ID: <20070223155247.15333.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30853-14108@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from sdack at gmx dot de  2007-02-23 15:52 -------
Subject: Re:  warnings about traditional.c during
 bootstrap with -O3, leading to internal error

> >   Still, I find it a bit scary installing gcc without first
> bootstrapping it. I
> > trust the result more than without it.
> 
> --enable-bootstrap is not the flag which enables bootstrap but instead it
> enables toplevel bootstrap which is not supported in 4.1.x.
> 
> "make bootstrap" without --enable-bootstrap will do a normal bootstrap and
> should just work.
> 
> So closing as invalid.

Of course I ran make with "bootstrap" and with "profiledbootstrap". It still
fails to compile with a BOOT_CFLAGS set to -O3.

Since this is the section for reporting bugs and problems with bootstrap,
please explain to me why you changed the severity from major to minor. When you
tell me not to use the option at all I consider it to be broken and that is
surely not a minor problem!

I still fail to bootstrap with -O3.

Please explain why you close the report as being invalid.

Sven


-- 


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


      parent reply	other threads:[~2007-02-23 15:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-18 23:44 [Bug bootstrap/30853] New: " sdack at gmx dot de
2007-02-23  0:11 ` [Bug bootstrap/30853] " pinskia at gcc dot gnu dot org
2007-02-23 13:04 ` sdack at gmx dot de
2007-02-23 14:31 ` pinskia at gcc dot gnu dot org
2007-02-23 15:53 ` sdack at gmx dot de [this message]

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=20070223155247.15333.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).