public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "geoffk at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/32161] New: stage1 libgcc is being built unoptimized
Date: Thu, 31 May 2007 01:47:00 -0000 [thread overview]
Message-ID: <bug-32161-638@http.gcc.gnu.org/bugzilla/> (raw)
The stage1 libgcc.a and crt files are being built with -O0. This means that
the stage2 cc1 is using unoptimized libgcc.a, but the stage3 cc1 is using
optimized libgcc.a, which is causing them to be different, which is one of a
number of causes for
Comparing stages 2 and 3
warning: ./cc1-checksum.o differs
warning: ./cc1obj-checksum.o differs
warning: ./cc1plus-checksum.o differs
on Darwin. I suspect this is related to PR 32009 but am not sure they're the
same bug.
--
Summary: stage1 libgcc is being built unoptimized
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: geoffk at gcc dot gnu dot org
GCC target triplet: *-*-darwin*
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32161
next reply other threads:[~2007-05-31 1:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 1:47 geoffk at gcc dot gnu dot org [this message]
2007-05-31 1:51 ` [Bug bootstrap/32161] " pinskia at gcc dot gnu dot org
2007-05-31 6:06 ` bonzini at gnu dot org
2007-08-31 21:34 ` zadeck at naturalbridge dot com
2007-09-02 11:29 ` bonzini at gnu dot org
2008-02-20 7:56 ` bonzini at gnu dot org
2008-02-20 7:56 ` bonzini at gnu dot org
2008-02-20 14:12 ` bonzini at gcc dot gnu dot org
2008-04-05 8:54 ` bonzini at gnu dot org
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=bug-32161-638@http.gcc.gnu.org/bugzilla/ \
--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).