Re: c++/1952

["Pete W." <pwitko71 at maine dot edu>]

The following reply was made to PR c++/1952; it has been noted by GNATS.

From: "Pete W." <pwitko71@maine.edu>
To: Craig Rodrigues <rodrigc@mediaone.net>
Cc:  
Subject: Re: c++/1952
Date: Sat, 17 Feb 2001 16:16:59 -0500 (EST)

 It seems as though it should, I did, after much staring at the code, realize the
 array was too large to be allocated that way.  I only bothered to file the bug
 report since 2.95.2 (I think?  I'm not on the system that had the problem atm)
 on osf did produce a compiler bug error message, and similar code did compile
 and segfaulted imediately.  But it looks to be fixed in the development
 version.  Thanks very much for trying this out, and for your work on gcc.
 
 Peter
 
 Quoting Craig Rodrigues <rodrigc@mediaone.net>:
 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=1952&database=gcc
 > 
 > Compiling your test case with the following version of gcc:
 > gcc version 2.97 20010211 (experimental)
 > 
 > Yielded the following errors, but not internal compiler errors:
 > 
 > I took your test-case and modified it a bit (it's attached).  Compiling
 > it
 > yielded:
 >  g++ -c gapsort.compiler_bug.cpp
 > gapsort.compiler_bug.cpp: In function `int main(int, char**)':
 > gapsort.compiler_bug.cpp:63: parse error before `;' token
 > gapsort.compiler_bug.cpp:56: confused by earlier errors, bailing out
 > 
 > Also, on line 56, you may be allocating too much space for your
 > array at compile time.  You may want to malloc that instead.
 > 
 > Should this report be closed?
 > --
 > Craig Rodrigues
 > http://www.gis.net/~craigr
 > rodrigc@mediaone.net
 > 
 > 
 
 
 
 *********************************************************
 * Peter W. (petew@linuxstart.com || Pwitko71@maine.edu) *
 *********************************************************