From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: linuxppc-dev@lists.linuxppc.org,
"Thomas C. Allison" <allison@dirac.nist.gov>,
linuxppc-user@lists.linuxppc.org
Subject: Re: possible egcs c compiler bug
Date: Wed, 19 May 1999 23:26:37 +0200 [thread overview]
Message-ID: <99051923331400.00882@ns1102.munich.netsurf.de> (raw)
In-Reply-To: 199905192019.QAA00884@dirac.nist.gov
Am Wed, 19 May 1999 schrieb Thomas C. Allison:
>I have found what *appears* to be a bug in the C compiler. I have experienced
>this bug in R4 (regardless of the compiler/library installed) as well as in
>the latest (i.e. all the latest packages through 5/15/1999) pre-R5
>installation. I include a short program below which illustrates the problem
>I am having. The code compiles without error on my i386 machine
>running RHL 5.2. The version of EGCS on the PC is 1.0.3 versus 1.1.2 on my
>PowerMac, so I don't know if this is a PPC problem or an EGCS problem.
>Any input is greatly appreciated.
>
>The code is as follows:
>
>test.c:
>
> #include <stdio.h>
> #include <stdarg.h>
>
> static int myFunction(va_list inList)
> {
> va_list newList;
> newList = inList;
> }
>
>When I try to compile the code
>
> % gcc -c test.c
>
>I get the following error message
>
> test.c: In function `myFunction':
> test.c:7: incompatible types in assignment
>
>Any ideas?
That is simply unportable code. va_list maybe of any underlying type, and is in
this case an array. If you want portable code, use:
static int myFunction(va_list inList)
{
va_list newList;
__va_copy(newList, inList);
}
If you use varargs extensively in your application, I strongly recommend you to
use egcs-*1.1.2-12c or later on DRR1/preR5, which fixes some annoying bugs
in the ppc-linux varargs handling.
Franz.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
prev parent reply other threads:[~1999-05-19 21:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-19 20:19 possible egcs c compiler bug Thomas C. Allison
1999-05-19 20:56 ` Brad Boyer
1999-05-19 21:04 ` Hartmut Koptein
1999-05-19 21:26 ` Franz Sirl [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=99051923331400.00882@ns1102.munich.netsurf.de \
--to=franz.sirl-kernel@lauterbach.com \
--cc=allison@dirac.nist.gov \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-user@lists.linuxppc.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 NNTP newsgroup(s).