From: Brad Boyer <flar@cegt201.bradley.edu>
To: allison@dirac.nist.gov (Thomas C. Allison)
Cc: linuxppc-user@lists.linuxppc.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: possible egcs c compiler bug
Date: Wed, 19 May 1999 15:56:30 -0500 (CDT) [thread overview]
Message-ID: <199905192056.PAA21815@cegt201.bradley.edu> (raw)
In-Reply-To: <199905192019.QAA00884@dirac.nist.gov> from "Thomas C. Allison" at May 19, 99 04:19:17 pm
> 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.
"It's not a bug, it's a feature"...
You're using something that is not technically the proper way to use
va_list in your code. However, that code works on everything but ppc.
It has to do with the way va_list is implemented on any ppc platform,
and causes all sorts of strange things to happen when you don't follow
the spec close enough. Find a better way to copy the va_list. Just
using the = operator isn't enough on ppc. Use a block copy of
sizeof(va_list) bytes, or some such. This has come up before, so if
you search the list archives, you should find sample code. Someone
else could give a lot more details on this. I only know the general
overview.
Brad Boyer
flar@cegt201.bradley.edu
[[ 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. ]]
next prev parent reply other threads:[~1999-05-19 20:56 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 [this message]
1999-05-19 21:04 ` Hartmut Koptein
1999-05-19 21:26 ` Franz Sirl
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=199905192056.PAA21815@cegt201.bradley.edu \
--to=flar@cegt201.bradley.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.