public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: green@simba.cygnus.com
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/4200: bootstrap comparison problem on IA-64
Date: Sat, 01 Sep 2001 11:46:00 -0000 [thread overview]
Message-ID: <200109011829.f81ITNE23781@simba.cygnus.com> (raw)
>Number: 4200
>Category: bootstrap
>Synopsis: bootstrap comparison problem on IA-64
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: wrong-code
>Submitter-Id: net
>Arrival-Date: Sat Sep 01 11:46:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:
>Release: 3.1 20010831 (experimental)
>Organization:
>Environment:
System: Linux simba.cygnus.com 2.4.7-2 #1 Tue Aug 14 04:44:26 EDT 2001 ia64 unknown
Architecture: ia64
host: ia64-unknown-linux-gnu
build: ia64-unknown-linux-gnu
target: ia64-unknown-linux-gnu
configured with: /simba2/green/gcj/gcc/configure --enable-threads --enable-languages=c++,java --prefix=/simba2/green/gcj/i
>Description:
make bootstrap with the trunk on IA-64 Linux results in...
Bootstrap comparison failure!
alias.o differs
bb-reorder.o differs
c-aux-info.o differs
c-common.o differs
c-convert.o differs
c-decl.o differs
c-dump.o differs
c-errors.o differs
c-format.o differs
c-lang.o differs
c-lex.o differs
combine.o differs
c-parse.o differs
cppdefault.o differs
cpperror.o differs
cppexp.o differs
cppfiles.o differs
cpphash.o differs
cppinit.o differs
cpplex.o differs
cpplib.o differs
cppmacro.o differs
c-pragma.o differs
c-semantics.o differs
c-typeck.o differs
fold-const.o differs
gcov.o differs
ggc-page.o differs
hashtable.o differs
ia64.o differs
ifcvt.o differs
insn-emit.o differs
insn-opinit.o differs
insn-peep.o differs
integrate.o differs
jump.o differs
lcm.o differs
line-map.o differs
lists.o differs
local-alloc.o differs
loop.o differs
mbchar.o differs
mkdeps.o differs
optabs.o differs
params.o differs
predict.o differs
prefix.o differs
print-tree.o differs
profile.o differs
real.o differs
recog.o differs
regclass.o differs
regmove.o differs
regrename.o differs
reg-stack.o differs
reload1.o differs
reload.o differs
reorg.o differs
resource.o differs
rtlanal.o differs
rtl-error.o differs
sbitmap.o differs
sched-deps.o differs
sched-ebb.o differs
sched-rgn.o differs
sched-vis.o differs
sdbout.o differs
sibcall.o differs
simplify-rtx.o differs
ssa-ccp.o differs
ssa-dce.o differs
ssa.o differs
stmt.o differs
stor-layout.o differs
stringpool.o differs
timevar.o differs
toplev.o differs
tradcif.o differs
tradcpp.o differs
tree.o differs
unroll.o differs
varasm.o differs
varray.o differs
xcoffout.o differs
cp/call.o differs
cp/class.o differs
cp/cvt.o differs
cp/decl2.o differs
cp/decl.o differs
cp/errfn.o differs
cp/error.o differs
cp/except.o differs
cp/expr.o differs
cp/friend.o differs
cp/init.o differs
cp/lex.o differs
cp/method.o differs
cp/parse.o differs
cp/pt.o differs
cp/ptree.o differs
cp/rtti.o differs
cp/search.o differs
cp/spew.o differs
cp/typeck2.o differs
make[1]: *** [compare] Error 1
>How-To-Repeat:
Check out the trunk and run make bootstrap.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2001-09-01 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-01 11:46 green [this message]
2001-09-06 11:27 wilson
2001-09-06 22:10 wilson
2001-09-13 14:53 wilson
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=200109011829.f81ITNE23781@simba.cygnus.com \
--to=green@simba.cygnus.com \
--cc=gcc-gnats@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).