All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas C. Allison" <allison@dirac.nist.gov>
To: linuxppc-user@lists.linuxppc.org
Cc: linuxppc-dev@lists.linuxppc.org
Subject: possible egcs c compiler bug
Date: Wed, 19 May 1999 16:19:17 -0400 (EDT)	[thread overview]
Message-ID: <199905192019.QAA00884@dirac.nist.gov> (raw)


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?

Thanks in advance,

Tom

+------------------------------------------------------------------------------+
| Dr. Thomas C. Allison                          | thomas.allison@nist.gov     |
| Computational Chemistry Group                  | (301)975-2216 (voice)       |
| National Institute of Standards and Technology | (301)869-4020 (fax)         |
| 100 Bureau Drive, Stop 8380                    |                             |
| Gaithersburg, Maryland 20899-8380              |                             |
+------------------------------------------------------------------------------+
  Chemistry is applied theology.  --- Augustus Stanley Owsley III

[[ 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.   ]]

             reply	other threads:[~1999-05-19 20:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-05-19 20:19 Thomas C. Allison [this message]
1999-05-19 20:56 ` possible egcs c compiler bug Brad Boyer
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=199905192019.QAA00884@dirac.nist.gov \
    --to=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.