From: David Edelsohn <dje@watson.ibm.com>
To: satadru pramanik <satadru@umich.edu>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: compiler errors
Date: Wed, 13 Jan 1999 15:07:41 -0500 [thread overview]
Message-ID: <9901132007.AA42094@marc.watson.ibm.com> (raw)
In-Reply-To: Message from satadru pramanik <satadru@umich.edu> of "Wed, 13 Jan 1999 14:55:33 EST." <Pine.LNX.4.05.9901131455170.11281-100000@beer.pub.umich.edu>
>>>>> satadru pramanik writes:
satadru> egcs 1.1.1c
Hmm, well I thought that problem had been addressed in egcs-1.1.1.
The problem is that GCC is generating a memory reference with a
displacement (65536) which is larger than 16 bits. Someone needs to try
to track down why the PowerPC port thinks that is a valid address instead
of splitting it into an intermediate offset in a register.
Either GCC is generating that offset itself and the normal tests
for valid types of addressing are failing. Or, something in the PowerPC
port explicitly is generating a memory operation which bypasses the tests
and is not explicitly checking for exceeding this offset limit.
David
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1999-01-13 20:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-13 18:24 compiler errors satadru pramanik
1999-01-13 19:47 ` David Edelsohn
1999-01-13 19:55 ` satadru pramanik
1999-01-13 20:07 ` David Edelsohn [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-07-13 5:46 Compiler errors Marko Saukko
2009-07-13 11:26 ` Marcel Holtmann
2009-07-14 5:25 ` Marcel Holtmann
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=9901132007.AA42094@marc.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=satadru@umich.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.