public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: stuarty@stuartymcf.uklinux.net
To: gcc-gnats@gcc.gnu.org
Subject: c++/8630: Internal compiler error
Date: Sun, 24 Nov 2002 10:59:00 -0000 [thread overview]
Message-ID: <20021118221813.13030.qmail@sources.redhat.com> (raw)
>Number: 8630
>Category: c++
>Synopsis: Internal compiler error
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: ice-on-legal-code
>Submitter-Id: net
>Arrival-Date: Mon Nov 18 14:26:04 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: me
>Release: Reading specs from /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.2/specs
>Organization:
>Environment:
Debian 3.0, all of the gnu compilers were compiled from source, using "gcc version 2.95.4 20011002"
>Description:
initialising a 2d array with variables causes this:
TerrainMap.cpp: In constructor `TerrainMap::TerrainMap(char*, char*, int)':
TerrainMap.cpp:30: Internal compiler error in find_function_data, at function.c
:329
Please submit a full bug report,
with preprocessed source if appropriate.
>How-To-Repeat:
see code snippet included
>Fix:
use static array initialisers
>Release-Note:
>Audit-Trail:
>Unformatted:
Configured with: ./configure : (reconfigured) ./configure
Thread model: posix
gcc version 3.2
----gnatsweb-attachment----
Content-Type: text/x-c++src; name="code_snippet.cpp"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="code_snippet.cpp"
Ly8gVGhlIGNvbnN0cnVjdG9yIHRoYXQgY2F1c2VzIHRoZSBwcm9ibGVtCgpUZXJyYWluTWFwOjpU
ZXJyYWluTWFwKGNoYXIgKm1hcGZpbGUsIGNoYXIgKnRleHR1cmVmaWxlLCBpbnQgbWFwX3N0ZXAp
CnsKCUZJTEUgKmluID0gZm9wZW4oR2V0UGF0aChtYXBmaWxlKSwgInJiIik7CgoJaWYgKCFpbikg
CgkJcmV0dXJuOwoKCWxvbmcgbWFwX3NpemUgPSBHZXRGaWxlU2l6ZShpbik7CglmcHJpbnRmKHN0
ZGVyciwgIkdvdCBmaWxlIHNpemUgb2YgJWxkXG4iLCBtYXBfc2l6ZSk7CgoJdGV4dHVyZSA9IEdl
dFRleHR1cmUodGV4dHVyZWZpbGUsIFJFUEVBVCk7CglVaW50OCBidWZbbWFwX3NpemVdW21hcF9z
aXplXTsKCWZyZWFkKCZidWYsIChtYXBfc2l6ZSAqIG1hcF9zaXplKSwgMSwgaW4pOwoJaWYgKGZl
cnJvcihpbikpIHsKCQlTZXRFcnJvcigiRXJyb3IgcmVhZGluZyBmcm9tICVzXG4iLCBtYXBmaWxl
KTsKCQlyZXR1cm47Cgl9CgoJZ2xQdXNoTWF0cml4KCk7CglkaXNwX2xpc3QgPSBnbEdlbkxpc3Rz
KDEpOwoJZ2xOZXdMaXN0KGRpc3BfbGlzdCwgR0xfQ09NUElMRSk7CglnbFRyYW5zbGF0ZWYoLW1h
cF9zaXplID4+IDEsIDAsIC1tYXBfc2l6ZSA+PiAxKTsKCWZvciAoaW50IHkgPSAwOyB5IDwgbWFw
X3NpemUgLSBtYXBfc3RlcDsgeSArPSBtYXBfc3RlcCkgewoJCWdsQmVnaW4oIEdMX1RSSUFOR0xF
X1NUUklQICk7CgkJZm9yIChpbnQgeCA9IDA7IHggPCBtYXBfc2l6ZSAtIG1hcF9zdGVwOyB4Kz0g
bWFwX3N0ZXApIHsKCQkJZ2xUZXhDb29yZDJmKChmbG9hdCl4L21hcF9zaXplLCAoZmxvYXQpeS9t
YXBfc2l6ZSk7Ci8qb3JpZ2luYWwgbGluZSAzMSovCWdsVmVydGV4M2koeCwgKGludClidWZbeF1b
eV0sIHkpOwoJCQlnbFRleENvb3JkMmYoKGZsb2F0KXgvbWFwX3NpemUsIChmbG9hdCkoeSArIG1h
cF9zdGVwKS9tYXBfc2l6ZSk7CgkJCWdsVmVydGV4M2koeCwgKGludClidWZbeF1beSttYXBfc3Rl
cF0sIHkrbWFwX3N0ZXApOwoJCX0KCQlnbEVuZCgpOwoJfQoJZ2xFbmRMaXN0KCk7CglnbFBvcE1h
dHJpeCgpOwp9CgoKLy8gdGhlc2UgYXJlIGtlcHQgaW4gYSBkaWZmZXJlbnQgc291cmNlIGZpbGUg
YnV0IGFyZSBpbmNsdWRlZCBpbiBjYXNlIHRoZXJlIHJlbGV2YW50CiAKbG9uZyBHZXRGaWxlU2l6
ZShGSUxFICpmcCkKewoJbG9uZyBzYXZlID0gZnRlbGwoZnApOwoJZnNlZWsoZnAsIDAsIFNFRUtf
RU5EKTsKCWxvbmcgcmV0ID0gZnRlbGwoZnApOwoJZnNlZWsoZnAsIHNhdmUsIFNFRUtfU0VUKTsK
CXJldHVybiByZXQ7Cn0K
next reply other threads:[~2002-11-18 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-24 10:59 stuarty [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-24 14:33 Stuart McFadden
2002-11-24 10:59 reichelt
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=20021118221813.13030.qmail@sources.redhat.com \
--to=stuarty@stuartymcf.uklinux.net \
--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).