From: David Edelsohn <dje@watson.ibm.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: ia64 linux doesn't bootstrap
Date: Sat, 19 Oct 2002 01:09:00 -0000 [thread overview]
Message-ID: <200210190202.WAA30032@makai.watson.ibm.com> (raw)
In-Reply-To: Message from Mark Mitchell <mark@codesourcery.com> of "Fri, 18 Oct 2002 15:25:17 PDT." <5110000.1034979917@warlock.codesourcery.com>
>>>>> Mark Mitchell writes:
Mark> But, nobody should every be trying to read or write those bits. Why
Mark> is that happenning?
Mark> Anyhow, what is the triplet for the target? If I run bitfield7.C on
Mark> that target's cc1plus I take it I will see the failure?
The target triplet seems to be any PowerPC (:-) target:
powerpc-eabisim, powerpc-unknown-linux-gnu, powerpc-ibm-aix4.3.3.0 .
The failure, as Janis mentioned, is g++.dg/compat/break/bitfield7_y.C
which as an ABI compatibility test expands on the original
g++.dg/abi/bitfield7.C test. bitfield7.C *does not* access the field and
does not ICE. Only Janis's new test, bitfield7_y.C, operates on the
bitfield eliciting the ICE. This may be a failure which only visibly ICEs
on big-endian targets due to the logic in extract_bit_field.
David
next prev parent reply other threads:[~2002-10-19 2:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 4:53 Aldy Hernandez
2002-10-18 7:33 ` Tim Prince
2002-10-18 11:49 ` Jim Wilson
2002-10-19 7:39 ` Tim Prince
2002-10-22 15:23 ` Jim Wilson
2002-10-24 4:43 ` tprinceusa
2002-10-18 8:18 ` Andreas Schwab
2002-10-18 12:49 ` Janis Johnson
2002-10-18 12:53 ` David Edelsohn
2002-10-18 16:05 ` David Edelsohn
2002-10-18 17:04 ` Mark Mitchell
2002-10-18 17:12 ` Janis Johnson
2002-10-19 1:09 ` David Edelsohn [this message]
2002-10-21 3:28 ` Mark Mitchell
2002-10-21 18:03 ` Jim Wilson
2002-10-21 19:49 ` Janis Johnson
2002-10-20 6:16 ` Andreas Schwab
2002-10-20 9:43 ` Janis Johnson
2002-10-18 13:01 ` Aldy Hernandez
2002-10-21 20:34 Ulrich Weigand
2002-10-21 23:35 ` David Edelsohn
2002-10-22 10:43 ` Ulrich Weigand
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=200210190202.WAA30032@makai.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
/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).