public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Matthias Klose <doko@debian.org>
To: gcc-gnats@gcc.gnu.org, debian-gcc@lists.debian.org
Subject: other/9081: gcc doesn't diagnose, that the compiler exceeds a compiler limit
Date: Sat, 28 Dec 2002 06:06:00 -0000 [thread overview]
Message-ID: <E18SHUv-0007zK-00@tango.net.local> (raw)
>Number: 9081
>Category: other
>Synopsis: gcc doesn't diagnose, that the compiler exceeds a compiler limit
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: accepts-illegal
>Submitter-Id: net
>Arrival-Date: Sat Dec 28 06:06:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Pavel Machek <pavel@atrey.karlin.mff.cuni.cz>
>Release: 3.2.1 (Debian) (Debian unstable)
>Organization:
The Debian Project
>Environment:
System: Debian GNU/Linux (unstable)
Architecture: i686
host: i386-linux
Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,proto,pascal,objc,ada --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.2 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-clocale=gnu --enable-java-gc=boehm --enable-objc-gc i386-linux
Thread model: posix
gcc version 3.2.2 20021212 (Debian prerelease)
>Description:
[ Reported to the Debian BTS as report #133574.
Please CC 133574@bugs.debian.org on replies.
Log of report can be found at http://bugs.debian.org/133574 ]
The following buggy code is exceeding a compiler limit,
thus the code behaves undefined. There is a bug in the compiler also:
the compiler should diagnose that you exceed the limit, but there is
no reasonable way you could expect this code to work on the
microprocessor you are using (and with the operating system you are
using).
#define MAXLEN 20
#define MAXTAG 10
double speedup[MAXLEN][MAXLEN][MAXLEN][MAXLEN][MAXTAG][MAXTAG][MAXTAG];
void
init_speedup(void)
{
int i, j, k, l, o, m, n;
for (i=0; i<MAXLEN; i++)
for (j=0; j<MAXLEN; j++)
for (k=0; k<MAXLEN; k++)
for (l=0; l<MAXLEN; l++)
for (o=0; o<MAXTAG; o++)
for (m=0; m<MAXTAG; m++)
for (n=0; n<MAXTAG; n++)
speedup[i][j][k][l][o][m][n] = -1.0;
}
int main(void)
{
init_speedup();
return 0;
}
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-12-28 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-28 6:06 Matthias Klose [this message]
2003-01-26 9:43 rth
2003-01-26 20:06 Pavel Machek
2003-01-28 2:46 Peter Bergner
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=E18SHUv-0007zK-00@tango.net.local \
--to=doko@debian.org \
--cc=133574@bugs.debian.org \
--cc=debian-gcc@lists.debian.org \
--cc=gcc-gnats@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).