From: Gunther Nikl <gnikl@users.sourceforge.net>
To: Ian Lance Taylor <iant@google.com>
Cc: Fabian Cenedese <Cenedese@indel.ch>, gcc-help@gcc.gnu.org
Subject: Re: Old gcc method parameter error
Date: Mon, 03 Oct 2011 15:03:00 -0000 [thread overview]
Message-ID: <4E89CEC1.7030906@users.sourceforge.net> (raw)
In-Reply-To: <mcrpqih3h80.fsf@coign.corp.google.com>
Ian Lance Taylor wrote:
> Gunther Nikl <gnikl@users.sourceforge.net> writes:
>
>> I am in no way a PPC expert, but AFAICT it seems to me that GCC
>> 2.95.2/GCC 2.95.3 had a bug with argument passing and it looks
>> like that the bug is fixed with 2.95.4 (from the CVS branch of
>> GCC 2.95):
>
> Interesting. That suggests that you need a patch like this one
>
> http://gcc.gnu.org/ml/gcc-patches/1999-11n/msg00616.html
>
> See revision 41152 in the SVN repository.
Indeed, that patch is the fix for the described problem.
prev parent reply other threads:[~2011-10-03 15:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 13:26 Fabian Cenedese
2011-09-29 21:20 ` Ian Lance Taylor
2011-09-30 20:31 ` Gunther Nikl
2011-10-03 6:59 ` Fabian Cenedese
[not found] ` <mcrpqih3h80.fsf@coign.corp.google.com>
2011-10-03 15:03 ` Gunther Nikl [this message]
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=4E89CEC1.7030906@users.sourceforge.net \
--to=gnikl@users.sourceforge.net \
--cc=Cenedese@indel.ch \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.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).