From: Ramon Bertran Monfort <rbertran@ac.upc.edu>
To: gcc-help@gcc.gnu.org
Subject: Stricter requirements for function main signature
Date: Mon, 07 Apr 2008 18:37:00 -0000 [thread overview]
Message-ID: <20080407164106.GA11348@rbertran-workstation> (raw)
Hello,
I guess that this is the correct place to ask the following question.
I've built a crosstoolchain for building Cell binaries on a x86 platform.
The gcc version I used is gcc 4.3.0 . When I compile spu binaries with the
corresponding main function signature...
main(unsigned long long spe, unsigned long long argp, unsigned long long
envp)
... I get an error telling me that the main signature is not correct (the
first parameters must be and integer, etc...).
spumain.cpp:56: error: first argument of 'int main(long long unsigned int,
long long unsigned int, long long unsigned int)' should be 'int'
spumain.cpp:56: error: second argument of 'int main(long long unsigned int,
long long unsigned int, long long unsigned int)' should be 'char **'
spumain.cpp:56: error: third argument of 'int main(long long unsigned int,
long long unsigned int, long long unsigned int)' should probably be 'char
**'
I've seen in http://www.gnu.org/software/gcc/gcc-4.3/porting_to.html that
C++ from version 4.3.0 has stricter requirements for function main
signature. How is supposed to work this on a Cell platform?
Thanks in advance,
Salut!
next reply other threads:[~2008-04-07 16:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 18:37 Ramon Bertran Monfort [this message]
2008-04-08 10:22 ` Andrew Haley
2008-04-08 13:17 ` Ramon Bertran Monfort
2008-04-08 14:56 ` Andrew Haley
2008-04-08 18:08 ` Ramon Bertran Monfort
2008-04-08 16:34 ` Jim Wilson
2008-04-08 18:33 ` Ramon Bertran Monfort
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=20080407164106.GA11348@rbertran-workstation \
--to=rbertran@ac.upc.edu \
--cc=gcc-help@gcc.gnu.org \
/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).