From: David Edelsohn <dje@watson.ibm.com>
To: Ulrich Weigand <weigand@immd1.informatik.uni-erlangen.de>
Cc: mark@codesourcery.com, gcc@gcc.gnu.org, janis187@us.ibm.com
Subject: Re: ia64 linux doesn't bootstrap
Date: Mon, 21 Oct 2002 23:35:00 -0000 [thread overview]
Message-ID: <200210220118.VAA28590@makai.watson.ibm.com> (raw)
In-Reply-To: Message from Ulrich Weigand <weigand@immd1.informatik.uni-erlangen.de> of "Tue, 22 Oct 2002 02:11:43 +0200." <200210220011.CAA25316@faui11.informatik.uni-erlangen.de>
>>>>> Ulrich Weigand writes:
Ulrich> I haven't analysed why extract_bit_field is called like that.
This is explained in my earlier message analyzing the failure. It
is called like that because the width of the bitfield exceeds its type yet
DECL_BIT_FIELD is set true. When DECL_BIT_FIELD is true, the call to
get_inner_reference() sets the MODE to BLKmode which causes
extract_bit_field() to be used to access the bits. extract_bit_field()
wants to step through the offsets in the word and ends up referring to
word -1 on big-endian targets.
David
next prev parent reply other threads:[~2002-10-22 1:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 20:34 Ulrich Weigand
2002-10-21 23:35 ` David Edelsohn [this message]
2002-10-22 10:43 ` Ulrich Weigand
-- strict thread matches above, loose matches on Subject: below --
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
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
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=200210220118.VAA28590@makai.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=janis187@us.ibm.com \
--cc=mark@codesourcery.com \
--cc=weigand@immd1.informatik.uni-erlangen.de \
/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).