From: Senthil Kumar Selvaraj <senthil_kumar.selvaraj@atmel.com>
To: Umesh Kalappa <Umesh.Kalappa@TOSHIBA-TSIP.COM>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>, <mikestump@comcast.net>
Subject: Re: [Testsuite] getpid in gcc.c-torture/execute/pr58419.c
Date: Tue, 28 Jan 2014 11:02:00 -0000 [thread overview]
Message-ID: <20140128065111.GB810@atmel.com> (raw)
In-Reply-To: <D70144161FA8C34E96606F874775290009CDE451@TOSBLRMBX01.TOSHIBA-TSIP.COM>
This is on trunk - I was under the impression that it is always trunk,
unless otherwise stated?
getpid doesn't really make sense for bare metal targets, I would think?
Regards
Senthil
On Mon, Jan 27, 2014 at 01:04:48PM +0000, Umesh Kalappa wrote:
> Senthil,
> Please do let us know the gcc version ,I couldn't locate the file pr58419.c in the GCC 4.8.1 source .
>
> To go with the below problem ,you can attributed the getpid() function as weak (http://www.embedded-bits.co.uk/2008/gcc-weak-symbols/).
>
> ~Umesh
>
> -----Original Message-----
> From: gcc-owner@gcc.gnu.org [mailto:gcc-owner@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 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
next prev parent reply other threads:[~2014-01-28 6:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-27 11:15 Senthil Kumar Selvaraj
[not found] ` <D70144161FA8C34E96606F874775290009CDE451@TOSBLRMBX01.TOSHIBA-TSIP.COM>
2014-01-28 11:02 ` Senthil Kumar Selvaraj [this message]
2014-01-28 18:40 ` Janis Johnson
2014-01-28 21:39 ` Jeff Law
[not found] <54196F45A68D5F44A17DBFF39883E26F84DE25B2@penmbx02.corp.atmel.com>
[not found] ` <5357EA80.1090900@redhat.com>
2014-04-25 9:16 ` Dhakshinamoorthy, Soundararajan
2014-04-30 21:09 ` Jeff Law
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=20140128065111.GB810@atmel.com \
--to=senthil_kumar.selvaraj@atmel.com \
--cc=Umesh.Kalappa@TOSHIBA-TSIP.COM \
--cc=gcc@gcc.gnu.org \
--cc=mikestump@comcast.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).