Rockbox.org home
release
dev builds
extras
themes manual
wiki
device status forums
mailing lists
IRC bugs
patches
dev guide



Rockbox mail archive

Subject: Re: Segfault with Faster MDCT patch and -fPIC

Re: Segfault with Faster MDCT patch and -fPIC

From: Dave Hooper <dave_at_beermex.com>
Date: Mon, 20 Sep 2010 18:17:31 +0100

More like bad (or at least) ambiguous code that I'm not surprised gcc
treated differently to how the author expected/intended (see all the
subsequent replies on the thread)
> On 20.09.2010 11:02, Slawomir Testowy wrote:
>> 2010/9/18 Nils Wallménius<nils.wallmenius_at_gmail.com>:
>>> gcc lets you specify the pic register with -mpic-register= so it would
>>> be a qucick test to try with r11 or something.
>>>
>>> Nils
>>>
>> Unfortunately, this doesn't work:
>>
>>
>> configure:3276: checking whether the C compiler works
>> configure:3298:
>>
/opt/freescale/usr/local/gcc-4.1.2-glibc-2.5-nptl-3/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-gcc
>> -std=gnu89 -g -ffast-math -fsingle-precision-constant
>> -mpic-register=r11 -fPIC -DPIC conftest.c>&5
>> conftest.c:1: error: unable to use 'r11' for PIC register
>> configure:3302: $? = 1
>> configure:3340: result: no
>>
>> The same happends with r12 register. Registers r1-10 are used directly
>> in the assembly.
>>
>
>
> Is this a bug in gcc? It's supposed to work.
>
> Best regards.
Received on 2010-09-20


Page was last modified "Jan 10 2012" The Rockbox Crew
aaa