public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: anthony@anthonyw.cjb.net
To: gcc-gnats@gcc.gnu.org
Subject: c++/7807: g++ 3.2 Fails to compile legal code that compiled OK with g++ 3.1
Date: Mon, 02 Sep 2002 02:36:00 -0000 [thread overview]
Message-ID: <20020902092927.13577.qmail@sources.redhat.com> (raw)
>Number: 7807
>Category: c++
>Synopsis: g++ 3.2 Fails to compile legal code that compiled OK with g++ 3.1
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Sep 02 02:36:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Anthony Williams
>Release: g++-3.2-mingw32
>Organization:
>Environment:
g++-3.2-mingw32
mingw-runtime 2.1
w32api 1.5
>Description:
The attached file produces errors about "uninitialized const member"s on g++ 3.2, but doesn't with g++ 3.1, nor if you remove the member function pointer from the RawMem union.
>How-To-Repeat:
Compile the attached file
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="cpp_regress.ii"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="cpp_regress.ii"
IyAxICJjcHBfcmVncmVzcy5jcHAiDQojIDEgIjxidWlsdC1pbj4iDQojIDEgIjxjb21tYW5kIGxp
bmU+Ig0KIyAxICJjcHBfcmVncmVzcy5jcHAiDQppbnQgaTEsaTI7DQoNCm5hbWVzcGFjZSB1dGls
cw0Kew0KICAgIGNsYXNzIFVua25vd247DQoNCiAgICB0ZW1wbGF0ZTx0eXBlbmFtZSBUPg0KICAg
IHVuaW9uIFJhd01lbQ0KICAgIHsNCiAgICAgICAgY2hhciBkYXRhW3NpemVvZihUKV07DQogICAg
ICAgIFVua25vd24qIChVbmtub3duOjoqIHNtZHApOw0KICAgIH07DQp9DQoNCg0KDQogICAgdGVt
cGxhdGU8dHlwZW5hbWUgVCx0eXBlbmFtZSBVPg0KICAgIHN0cnVjdCBPd25pbmdSZWZQYWlyDQog
ICAgew0KICAgIHB1YmxpYzoNCiAgICAgICAgVCYgZmlyc3Q7DQogICAgICAgIFUmIHNlY29uZDsN
Cg0KICAgIHByaXZhdGU6DQogICAgICAgIHV0aWxzOjpSYXdNZW08aW50PiBwYWlyQnVmOw0KICAg
ICAgICBjb25zdCBib29sIG93bnNGbGFnOw0KDQogICAgcHVibGljOg0KDQogICAgICAgIE93bmlu
Z1JlZlBhaXIoY29uc3QgT3duaW5nUmVmUGFpciYgb3RoZXIpOg0KICAgICAgICAgICAgZmlyc3Qo
aTEpLA0KICAgICAgICAgICAgc2Vjb25kKGkyKSwNCiAgICAgICAgICAgIG93bnNGbGFnKHRydWUp
DQogICAgICAgIHsNCiAgICAgICAgfQ0KDQoNCg0KICAgICAgICB0ZW1wbGF0ZTx0eXBlbmFtZSBW
YWwxLHR5cGVuYW1lIFZhbDI+DQogICAgICAgIE93bmluZ1JlZlBhaXIoY29uc3QgVmFsMSYgZmly
c3RfLGNvbnN0IFZhbDImIHNlY29uZF8pOg0KICAgICAgICAgICAgZmlyc3QoaTEpLA0KICAgICAg
ICAgICAgc2Vjb25kKGkyKSwNCiAgICAgICAgICAgIG93bnNGbGFnKHRydWUpDQogICAgICAgIHsN
CiAgICAgICAgfQ0KDQoNCg0KICAgIH07DQoNCg0KT3duaW5nUmVmUGFpcjxpbnQsaW50PiBhKGkx
LGkyKTsNCk93bmluZ1JlZlBhaXI8aW50LGludD4gYj1hOw0K
next reply other threads:[~2002-09-02 9:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-02 2:36 anthony [this message]
2002-09-02 8:06 Andris Pavenis
2002-09-13 13:35 nathan
2002-09-28 22:56 Pop Sébastian
2002-10-16 12:41 mmitchel
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=20020902092927.13577.qmail@sources.redhat.com \
--to=anthony@anthonyw.cjb.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).