Re: Internal Compiler Error 252

["Martin v. Loewis" <martin@mira.isdn.cs.tu-berlin.de>]

> YMain.cpp:222: Internal compiler error 252.
> YMain.cpp:222: Please submit a full bug report to
> `egcs-bugs@egcs.cygnus.com'.

Thanks for your bug report. gcc-2.95 19990701 compiles this just fine,
so it appears that the bug has been fixed.

Regards,
Martin
>From martin@mira.isdn.cs.tu-berlin.de Fri Jul 16 00:57:00 1999
From: "Martin v. Loewis" <martin@mira.isdn.cs.tu-berlin.de>
To: khaley@bigfoot.com
Cc: khan@xraylith.wisc.edu, egcs-bugs@egcs.cygnus.com
Subject: Re: Wrong delete being called.
Date: Fri, 16 Jul 1999 00:57:00 -0000
Message-id: <199907160749.JAA00745@mira.isdn.cs.tu-berlin.de>
References: <4.1.19990714001252.009455a0@pop.mail.yahoo.com>
X-SW-Source: 1999-07/msg00604.html
Content-length: 1149

> I have a base class with operator delete declared private.  The destructor
> of a derived class tries to delete a pointer held by the base class but it
> can't.  The compiler reports that operator delete is private which is true,
> however it is not the delete that should be called.

Thanks for your bug report. Please note that the compiler also reports
the error if you write

   ~TPointer() {}

The problem is not deleting P, but deleting a TPointer instance. To
delete a TPointer instance, the appropriate delete operator must be
found. Since the base class has a delete operator, it is the one to
use. Unfortunately, the delete operator is private, so it can't be
used.

This shows up in the TPointer destructor, because in g++, the
deallocation functions are called in the destructor (to correctly
support virtual destructors).

There is a slight bug in g++ here: It should complain only when
somebody allocates or deletes instances of TPointerBase or
TPointer. This does not happen here, so it shouldn't complain.

As a work-around, it seems that you'll have to remove the private
operator delete when compiling with g++.

Regards,
Martin
>From max@takefive.co.at Fri Jul 16 01:47:00 1999
From: Max Weninger <max@takefive.co.at>
To: egcs-bugs@egcs.cygnus.com
Subject: Bugreport
Date: Fri, 16 Jul 1999 01:47:00 -0000
Message-id: <199907160847.KAA02563@extreme.takefive.co.at>
X-SW-Source: 1999-07/msg00605.html
Content-length: 2189

Hi,

I discovered a (in my opinion) bug in the latest gcc-2.95 prerelease.

-------------------------------------------------------------------------------------
Compiler Info:

Reading specs from /opt/gcc-dev/lib/gcc-lib/alphaev56-unknown-linux-gnu/2.95/specs
gcc version 2.95 19990712 (prerelease)

--------------------------------------------------------------------------------------

Source Code:

#include <iostream>
        enum EFlags {
                eFirst =0x00001000,
                eLast =0x80000000
        };
        enum EFlags1 {
                eFlags1       = eFirst << 11
        };
        enum EFlags2 {
                eFlags2    = eFlags1 << 1
        };
        enum EFlags3 {
                eFlags3       = eFlags2<< 7
        };
        enum EFlags4 {
                eFlags4        = eFirst << 19
        };
int main( int, char **)
{
        cerr << eFlags3<< endl;
        cerr << eFlags4<< endl;
}

----------------------------------------------------------------------------------------
Compile options:

g++ shift.C 

----------------------------------------------------------------------------------------

Description:

extreme /tmp/test> ./a.out
-2147483648
2147483648

Why is eFlags3 negative ?

If you remove the eLast Flags from the EFlags enum 

        enum EFlags {
                eFirst =0x00001000
        };

the result is

extreme /tmp/test> ./a.out
-2147483648
-2147483648

No both results are negative

---------------------------------------------------------------------

System Information:

Linux extreme 2.2.5 #4 Thu Jun 17 18:18:13 CEST 1999 alpha unknown
RedHat 5.2 on a 21164a 600MHz Alpha

----------------------------------------------------------------------

Regards

Max

-- 
_______________________________________________________________
     \                  
    o/\_          DI Max Weninger
   <\__,\         Email (max@takefive.co.at)          
    ">.  |         
     ` .-|        TakeFive Software - Jakob-Haringer-Str. 8
        . \       A-5020 Salzburg - AUSTRIA
         . \      Tel: +43 662 4579150 - Fax: +43 662 4579156
         .-|      
_________._|____________________________________________________