From: Albrecht Dre_ <ad@mpifr-bonn.mpg.de>
To: LinuxPPC Users <linuxppc-user@lists.linuxppc.org>
Cc: LinuxPPC-Dev Liste <linuxppc-dev@lists.linuxppc.org>
Subject: gcc 2.95/PPC bug
Date: Fri, 21 Jan 2000 08:03:47 +0100 [thread overview]
Message-ID: <388804D3.DF16EE2F@mpifr-bonn.mpg.de> (raw)
When trying to find the cause for crashes of LAME, I think I found a
bug in the gcc. The code below (which is actually a simpilified excerpt
from LAME) will NOT pass the parameter `buggy' correctly to the
subroutine. Changing the number/type/sorting of the parameters will,
however, produce a working code in some cases. Some facts about the
system:
Machines: PowerMac 7300 (604e), LinuxPPC 2.2.11
PB "Lombard" (G3), LinuxPPC 2.2.12
gcc: versions 2.95 and 2.95.1
options: gcc -O0 -Wall gcc-2.95-ppc-bug.c -o gcc-2.95-ppc-bug
Is this a known (and hopefully already fixed ;-) bug, or should it go
directly to gcc-bugs@gcc.gnu.org?
Thanks, Albrecht.
---snip here:gcc-2.95-ppc-bug.c-----------------------------------------------
#include <stdio.h>
void vartest (double xr[2][2][576],
int l3_enc[2][2][576],
int var1, int var2, int var3, int var4, int var5, int var6,
int var7, int var8, int var9, double var10, int buggy)
{
printf ("%d %d %d %d %d %d %d %d %d %g %d\n",
var1, var2, var3, var4, var5, var6, var7, var8, var9, var10, buggy);
}
int main ()
{
double xxx [2][2][576];
int eee [2][2][576];
vartest (xxx, eee, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10.1, 11);
return 0;
}
---end of bug demo code-------------------------------------------------------
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-01-21 7:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-21 7:03 Albrecht Dre_ [this message]
2000-01-21 15:37 ` gcc 2.95/PPC bug Franz Sirl
2000-01-24 9:53 ` Albrecht Dre_
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=388804D3.DF16EE2F@mpifr-bonn.mpg.de \
--to=ad@mpifr-bonn.mpg.de \
--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.