On 04/25/14 03:16, Dhakshinamoorthy, Soundararajan wrote:
2014-04-25 Soundararajan Dhakshinamoorthy
* gcc.c-torture/execute/pr58419.c: Adjust the test to work with bare
metal targets. The
test code references to functions that is not implemented for the
avr target (getpid(
u.org
Subject: Re: [Testsuite] getpid in gcc.c-torture/execute/pr58419.c
On 04/23/14 05:50, Dhakshinamoorthy, Soundararajan wrote:
> Hi all,
>
> The test mentioned in the link had a call to getpid which causes the test to
> fail for bare metal targets. Is it ok to replace it
On 01/28/14 11:14, Janis Johnson wrote:
The testcase in the PR had a call to printf. The modified test doesn't call
printf, and doesn't declare getpid. I assume that getpid is called simply
to have an external call, but there must be something that could be used
instead that is available for an
n as
>> weak (http://www.embedded-bits.co.uk/2008/gcc-weak-symbols/).
>>
>> ~Umesh
>>
>> -Original Message-
>> From: gcc-ow...@gcc.gnu.org [mailto:gcc-ow...@gcc.gnu.org] On Behalf Of
>> Senthil Kumar Selvaraj
>> Sent: 27 January 2014 15:18
>&g
ssage-
> From: gcc-ow...@gcc.gnu.org [mailto:gcc-ow...@gcc.gnu.org] On Behalf Of
> Senthil Kumar Selvaraj
> Sent: 27 January 2014 15:18
> To: gcc@gcc.gnu.org
> Subject: [Testsuite] getpid in gcc.c-torture/execute/pr58419.c
>
> All,
>
> gcc.c-torture/execute/pr58419.c
All,
gcc.c-torture/execute/pr58419.c has a call to getpid, and this causes
a linker error on the AVR (embedded) target. Is the call intentional,
and if yes, how should this be fixed for targets that don't support an
OS?
Regards
Senthil
