On Sun, Mar 6, 2011 at 6:52 AM, Anthony Green wrote:
> On 3/6/2011 9:10 AM, H.J. Lu wrote:
>>
>> On Sun, Mar 6, 2011 at 5:57 AM, Dave Korn
>> wrote:
>>>
>>> On 06/03/2011 07:02, Anthony Green wrote:
All of the -flto tests fail for moxie-elf...
http://gcc.gnu.org/ml/gcc-testres
On 3/6/2011 9:10 AM, H.J. Lu wrote:
On Sun, Mar 6, 2011 at 5:57 AM, Dave Korn wrote:
On 06/03/2011 07:02, Anthony Green wrote:
All of the -flto tests fail for moxie-elf...
http://gcc.gnu.org/ml/gcc-testresults/2011-03/msg00399.html
It turns out that this is because it fails to link with the
On Sun, Mar 6, 2011 at 5:57 AM, Dave Korn wrote:
> On 06/03/2011 07:02, Anthony Green wrote:
>> All of the -flto tests fail for moxie-elf...
>>
>> http://gcc.gnu.org/ml/gcc-testresults/2011-03/msg00399.html
>>
>> It turns out that this is because it fails to link with the code in
>> libgloss when
On 06/03/2011 07:02, Anthony Green wrote:
> All of the -flto tests fail for moxie-elf...
>
> http://gcc.gnu.org/ml/gcc-testresults/2011-03/msg00399.html
>
> It turns out that this is because it fails to link with the code in
> libgloss when I enable -flto.
>
> I link the test code with a special
All of the -flto tests fail for moxie-elf...
http://gcc.gnu.org/ml/gcc-testresults/2011-03/msg00399.html
It turns out that this is because it fails to link with the code in
libgloss when I enable -flto.
I link the test code with a special linker script (sim.ld) that pulls in
the libgloss cod