Assembler could be fixed easily (I'll contribute the patch to MacPorts
cctools port) and the library is loading and working now.
So I suggest disabling the use of 64 bit instructions and registers
when targetting PowerPC Darwin 32 bit ABI can be considered working
and a patch to gcc shouldn't
Found the problem:
The assembler generates a relocation of type LO14, meaning 14 bits
that represent bits 2 - 15 of the effective address (lowest two bits
are forced to zero), which is used for some types of 64 bit loads and
stores.
Unfortunately the OS X dynamic linker doesn't support that
On Jan 1, 2013, at 10:03 AM, Tobias Netzel wrote:
> Or do you have any other ideas?
I don't. I'd grab the .s files (compile with -save-temps) and start stripping
things out til it loads, then then last thing stripped was the thing that broke
it.
Hi Iain, Mike and Andrew,
I have been having issues compiling WebKit with mcpu=970 (or mcpu=G5)
without afterwards passing mno-powerpc64 or m32 in to explicitly turn
64 bit instructions off.
That was using Apple gcc 5666.3, which is Apples last published
version and based on 4.2.1 .
I also
On 21 Jul 2012, at 19:02, Andrew Pinski wrote:
>> If there's a different mechanism for enforcing what's implied above, then we
>> could use
>
> Yes HARD_REGNO_CALL_PART_CLOBBERED should work. If that is not
> working there is a bug somewhere else in the compiler.
thanks, that looks solid enoug
On Sat, Jul 21, 2012 at 10:56 AM, Iain Sandoe wrote:
> Hi Mike,
>
> On 21 Jul 2012, at 18:27, Mike Stump wrote:
>
>> On Jul 21, 2012, at 9:12 AM, Iain Sandoe wrote:
>>> At present, if a G5 or 970 processor is selected (-mcpu=), we can (and do)
>>> generate 64 bit register usage for m32 code. Th
Hi Mike,
On 21 Jul 2012, at 18:27, Mike Stump wrote:
> On Jul 21, 2012, at 9:12 AM, Iain Sandoe wrote:
>> At present, if a G5 or 970 processor is selected (-mcpu=), we can (and do)
>> generate 64 bit register usage for m32 code. This appears to be a
>> long-standing bug.
>
> Hum, do you have
On Sat, Jul 21, 2012 at 10:27 AM, Mike Stump wrote:
> On Jul 21, 2012, at 9:12 AM, Iain Sandoe wrote:
>> At present, if a G5 or 970 processor is selected (-mcpu=), we can (and do)
>> generate 64 bit register usage for m32 code. This appears to be a
>> long-standing bug.
>
> Hum, do you have an
On Jul 21, 2012, at 9:12 AM, Iain Sandoe wrote:
> At present, if a G5 or 970 processor is selected (-mcpu=), we can (and do)
> generate 64 bit register usage for m32 code. This appears to be a
> long-standing bug.
Hum, do you have an example of something that fails? I ask, cause I think the
Hi,
At present, if a G5 or 970 processor is selected (-mcpu=), we can (and do)
generate 64 bit register usage for m32 code. This appears to be a
long-standing bug.
OK for trunk & all open branches?
Iain
gcc/
* config/rs6000/darwin.h (OS_MISSING_POWERPC64): New.
Index: gcc/c
10 matches
Mail list logo
