From: David Daney <ddaney@caviumnetworks.com>
To: keshav yadav <keshav.yadav2005@gmail.com>
Cc: Ian Lance Taylor <iant@google.com>,
mips-gnu-discuss@codesourcery.com, gcc-help@gcc.gnu.org
Subject: Re: page size change on MIPS
Date: Fri, 04 Feb 2011 17:47:00 -0000 [thread overview]
Message-ID: <4D4C39E5.6030403@caviumnetworks.com> (raw)
In-Reply-To: <mcr4o8j3gwf.fsf@google.com>
On 02/04/2011 08:26 AM, Ian Lance Taylor wrote:
> keshav yadav<keshav.yadav2005@gmail.com> writes:
>
>> I observe one different behavior when we have page size set to 4KB or
>> 16KB in kernel busybox receive argc[0] argument correct, but
>> when page size set to 64KB I am getting argv[0] as empty. So what may
>> be issue. I am using codesourcercy toolchain.
>
> I have no idea what the problem but I know that it is extremely unlikely
> to have anything to do with gcc.
>
I agree.
We routinely run programs compiled with a wide variety of stock GCC
versions, under all three MIPS/Linux ABIs (o32, n32, n64) on kernels
with 4K, 8K, 16K, 32K and 64K page sizes with no problems.
If you suspect a defect in your toolchain, you could try building a
'stock' toolchain with recent Binutils and GCC versions.
David Daney
next prev parent reply other threads:[~2011-02-04 17:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTik+vpiWR4Xk4Pu+uCHq3XO=BZMGVka8-B9vuQew@mail.gmail.com>
[not found] ` <4D3DCB5A.6060107@caviumnetworks.com>
[not found] ` <AANLkTin6GkKeJATbafP-k9YNcSTHeT8ohDpUD2RLDZ1J@mail.gmail.com>
[not found] ` <20110131130820.GB26217@linux-mips.org>
[not found] ` <AANLkTi=UTRk8e6fv3USP5RPKY-Fg0ehGBXrf0bD8NthX@mail.gmail.com>
[not found] ` <AANLkTimCfioamQWGeRCFFN=OoWE7-PhGs2tCH+_9H=HO@mail.gmail.com>
2011-02-04 6:02 ` keshav yadav
2011-02-04 9:40 ` keshav yadav
2011-02-04 16:50 ` Ian Lance Taylor
2011-02-04 17:47 ` David Daney [this message]
2011-02-07 16:11 ` naveen yadav
2011-02-07 23:47 ` David Daney
2011-02-08 8:43 ` naveen yadav
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=4D4C39E5.6030403@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.com \
--cc=keshav.yadav2005@gmail.com \
--cc=mips-gnu-discuss@codesourcery.com \
/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).