possible with gcc 4.1.1 found

2006-10-22 Thread djh
Background: This problem was found by running gnu mp's "make check" script after an successfull "make". GNU MP home page: http://www.swox.com/gmp/ Problem discovered while "make checking" ... of programs from gmp-4.2.1.tar.bz2 $ /usr/local/bin/gcc -v Using built-in specs. Tar

[Bug c++/50881] New: ICE Segfault on compare this pointer with reference

2011-10-27 Thread djh at emss dot co.za
ame -a Linux djh-emssnew 3.0.0-12-generic-pae #20-Ubuntu SMP Fri Oct 7 16:37:17 UTC 2011 i686 i686 i386 GNU/Linux gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-linux-gnu/4.6.1/lto-wrapper Target: i686-linux-gnu Configured with: ../src/configure -v --with-pkgvers

[Bug c++/50881] ICE Segfault on compare this pointer with reference

2011-10-27 Thread djh at emss dot co.za
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50881 --- Comment #2 from Diederik 2011-10-27 09:26:41 UTC --- In the archive, see the file ccjiYBAm.out If this is not sufficient, I can upload a new one.

[Bug c++/50881] ICE Segfault on compare this pointer with reference

2011-10-27 Thread djh at emss dot co.za
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50881 --- Comment #4 from Diederik 2011-10-27 10:18:18 UTC --- Created attachment 25626 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25626 Preprocessed source file Preprocessed file attached as requested.

[Bug libstdc++/33903] New: Backtrace info in std::exception

2007-10-26 Thread djh at emss dot co dot za
Severity: normal Priority: P3 Component: libstdc++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: djh at emss dot co dot za http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33903

[Bug libstdc++/33903] Backtrace info in std::exception

2007-10-26 Thread djh at emss dot co dot za
-- djh at emss dot co dot za changed: What|Removed |Added Severity|normal |enhancement http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33903

[Bug libstdc++/33903] Backtrace info in std::exception

2007-11-01 Thread djh at emss dot co dot za
--- Comment #2 from djh at emss dot co dot za 2007-11-02 06:08 --- I am using debugger. After the exception is thrown, the program asserts. So I get a backtrace to the system fatal call, having no idea where the exception was thrown. I dont know about you guys but I find the .net/java

[Bug libstdc++/33903] Backtrace info in std::exception

2007-11-01 Thread djh at emss dot co dot za
--- Comment #4 from djh at emss dot co dot za 2007-11-02 06:54 --- This is a possible solution. Not ideal though, because, then all exceptions will be trigger the breakpoint at __cxa_throw. If however, I put a breakpoint in the catch in question, then I know I will get the exception

[Bug c++/36852] New: Two dimensional array in template method argument list incorrectly interpreted.

2008-07-16 Thread djh at emss dot co dot za
reted. Product: gcc Version: 4.3.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: djh at emss dot co dot za http://gcc.gnu.org/bugzilla/show_bu

[Bug c++/36852] Two dimensional array in template method argument list incorrectly interpreted.

2008-07-17 Thread djh at emss dot co dot za
--- Comment #2 from djh at emss dot co dot za 2008-07-17 12:47 --- I have successfully reproduced this problem: Create a header file with the following structure, saving it as "a.h": class A { public: template static T foo1(T [3][3]); }; template T A::foo

[Bug c++/36852] [4.3/4.4 Regression] Two dimensional array in template method argument list incorrectly interpreted.

2008-07-18 Thread djh at emss dot co dot za
--- Comment #4 from djh at emss dot co dot za 2008-07-18 07:13 --- using your t.h file, the following command "g++ -v -save-temps -x c++-header -c t.h -o .obj/test.gch/c++" gives the following output Using built-in specs. Target: i686-pc-linux-gnu Configured with: .