Bug#293957: gcc-3.3: No warning when initializing a variable with itself.

2005-02-06 Thread Ian Turner
Package: gcc-3.3 Version: 1:3.3.5-5 Severity: minor Consider the following C code: -- stuffage.c: CUT HERE -- void stuffage() { int foo = foo; } -- CUT HERE -- If you compile this as follows: gcc stuffage.c -Wall -c Then gcc will generate no output. This is a bug, because this program actual

Bug#185243: libstdc++3-dev: rope segfaults under heavy load

2003-03-18 Thread Ian Turner
19, 2003 at 01:50:58AM +, Philip Martin wrote: > Ian Turner <[EMAIL PROTECTED]> writes: > > > Here is the modified code, with some additional checks: > > With that code I get a crash when I use Debian's g++-3.0 version 1:3.0.4-7. > > I also have a gcc-3.2 tha

Bug#185242: Error in testcase program.

2003-03-18 Thread Ian Turner
As Philip Martin pointed out in bug 185242, the testcase program submitted is incorrect; having failed to return rval, the return value is undefined in the case that rval != max. Fixing this problem, I am unable to reproduce the bug on gcc-3.2 (though still on gcc-3.0). New source code appears

Bug#185243: libstdc++3-dev: rope segfaults under heavy load

2003-03-18 Thread Ian Turner
Good point, though changing the function to return rval in the other case seems to change the result not at all. I suspect that (due to luck) rval is on the stack in any case. Here is the modified code, with some additional checks: #include #include #include using namespace std; using names

Bug#185243: See also bug 185242

2003-03-17 Thread Ian Turner
See also bug 185242, which is nearly identical but refers to libstdc++5-dev.

Bug#185243: Error in submission.

2003-03-17 Thread Ian Turner
In the submission of this bug, I made an error. $ ./ropetest-320 Aborted should instead read $ ./ropetest-300 Segmentation Fault My apologies. That's what I get for submitting two nearly-identical bug reports simultaneously. Ian Turner

Bug#185242: See also bug 185243

2003-03-17 Thread Ian Turner
See also bug 185243, which is the same bug as applied to listdc++3.

Bug#185242: libstdc++5-dev: rope segfaults under heavy load

2003-03-17 Thread Ian Turner
Package: libstdc++5-dev Version: 1:3.2.3-0pre5 Severity: important Consider the following program: --- BEGIN ropetest.c --- #include using namespace std; using namespace __gnu_cxx; unsigned int rand(unsigned int max) { unsigned int rval = (unsigned int)(((double)max)*rand()/(RAND_MAX)); if

Bug#185243: libstdc++3-dev: rope segfaults under heavy load

2003-03-17 Thread Ian Turner
Package: libstdc++3-dev Version: 1:3.0.4-7 Severity: important Consider the following program: --- BEGIN ropetest.c --- #include using namespace std; using namespace __gnu_cxx; unsigned int rand(unsigned int max) { unsigned int rval = (unsigned int)(((double)max)*rand()/(RAND_MAX)); if (rv

Bug#174598: gcc-3.2-doc: Bad link in documentation - C++ Extentions

2002-12-28 Thread Ian Turner
Package: gcc-3.2-doc Version: 1:3.2.1-0pre3 Severity: normal The page entitled "C++ Extensions" of gcc-3.2.info.gz contains the following paragraph: The GNU compiler provides these extensions to the C++ language (and you can also use most of the C language extensions in your C++ programs). I

Bug#173513: Wishlist: Inline constant function pointers

2002-12-17 Thread Ian Turner
Package: gcc-3.2 Version: 1:3.2.1-0pre3 Severity: wishlist Currently GCC will not inline a call of a function pointer that is known at compile time. For example, the following code will still result in the instruction "call funk" when run with -finline-functions on i386: #include static char*

Bug#169862: g++-3.2: vectors of vectors break with -ftrapv

2002-11-20 Thread Ian Turner
Package: g++-3.2 Version: 1:3.2.1-0pre3 Severity: important Not sure if this is a problem with the CPU, the kernel, the compiler, or the library. But this seems the most likely candidate. Consider the sample program below. When compiled as g++-3.2 foo.cc -ftrapv -o foo and run, the resultant b

Bug#168706: g++-3.0: Bad syntax error on nested classes' member functions.

2002-11-11 Thread Ian Turner
Package: g++-3.0 Version: 1:3.0.4-7 Severity: normal The source below makes G++-3.0 report a syntax error where none exists. Basically it doesn't wait before giving up on the typename. // Comment out to make it work. #define BREAK struct a { struct b { typedef unsigned int foo_t; foo_