With -fno-builtin the ICE does not happen.
*
This e-mail and any attachment is confidential. It may only be read, copied and
used by the intended recipient(s). If you are not the intended recipient(s),
you may not copy, use, d
Package: g++-3.2
Version: 1:3.2.1-0pre4
Severity: normal
Bang uptodate Debian testing/unstable g++-3.2 ICEs on this code.
Interestingly, it's already started generating the .s file. Dude on the gcc
bug list said to send it your way:
From: Andrew Pinski <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED
Martin,
Thanks for looking at this.
10.1.4 has this example, which it claims is legal (incidentally my g++-3.0
-pedantic agrees):
struct L { int next; };
struct A : L {};
struct B : L {};
struct C : A, B { void f (); };
void C::f () { A::next = B::next; }
If your previous transformation were a
>Submitter-Id: net
>Originator:
>Organization: BlueArc
>Confidential: no
>Synopsis: -pedantic reports ambiguous base
>Severity: non-critical
>Priority: low
>Category: c++
>Class: rejects-legal
>Release: 3.0.3 (Debian testing/unstable)
>Environment:
System:
Right, understood, finally. Thanks.
-Original Message-
From: Martin v. Loewis [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 24, 2001 8:43 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
debian-gcc@lists.debian.org; [EMAIL PROTECTED]
Subject: Re:
I can't disagree with your reading ("involve" doesn't mean "be"). However,
searching for "integral constant expression" suggests to me that this
outlaws the following code, all of which compiles without warning:
enum {dim = 1};
char a [dim]; // 8.3.4.1
void* b = new char [1] [dim]; // 5.3.4.6
st
6 matches
Mail list logo
