[Bug target/29639] FAIL: ext/bitmap_allocator/check_allocate_max_size.cc execution test

2006-10-30 Thread ebotcazou at gcc dot gnu dot org
--- Comment #5 from ebotcazou at gcc dot gnu dot org 2006-10-30 09:57 --- What is the command line to run only one test in the libstdc++ testsuite? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29639

[Bug target/29639] FAIL: ext/bitmap_allocator/check_allocate_max_size.cc execution test

2006-10-30 Thread pcarlini at suse dot de
--- Comment #6 from pcarlini at suse dot de 2006-10-30 11:48 --- (In reply to comment #5) What is the command line to run only one test in the libstdc++ testsuite? I'm reluctant to tell you in public, because certainly there are *far* better ways, but was I usually do when I'm in a

[Bug target/29639] FAIL: ext/bitmap_allocator/check_allocate_max_size.cc execution test

2006-10-30 Thread pcarlini at suse dot de
--- Comment #7 from pcarlini at suse dot de 2006-10-30 11:52 --- (In reply to comment #6) ... the complete command line from the ChangeLog. Of course read it 'libstdc++.log', sorry. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29639

[Bug target/29639] FAIL: ext/bitmap_allocator/check_allocate_max_size.cc execution test

2006-10-30 Thread ebotcazou at gcc dot gnu dot org
--- Comment #8 from ebotcazou at gcc dot gnu dot org 2006-10-30 12:02 --- I'm reluctant to tell you in public, because certainly there are *far* better ways, but was I usually do when I'm in a hurry, I simply go inside the libstdc++-v3/testsuite directory, set the LD_LIBRARY_PATH

[Bug target/29639] FAIL: ext/bitmap_allocator/check_allocate_max_size.cc execution test

2006-10-30 Thread pcarlini at suse dot de
--- Comment #9 from pcarlini at suse dot de 2006-10-30 12:05 --- (In reply to comment #8) The idea was precisely to avoid running the whole testsuite. :-) Oh, well, once in a while you *must* di that, right? ;) Just save somewhere libstdc++.log... --

[Bug target/29639] FAIL: ext/bitmap_allocator/check_allocate_max_size.cc execution test

2006-10-30 Thread ebotcazou at gcc dot gnu dot org
--- Comment #10 from ebotcazou at gcc dot gnu dot org 2006-10-30 14:49 --- Oh, well, once in a while you *must* di that, right? ;) Only under duress. :-) Bug confirmed with Binutils 2.17 20061003 on x86. -- ebotcazou at gcc dot gnu dot org changed: What|Removed

[Bug target/29639] FAIL: ext/bitmap_allocator/check_allocate_max_size.cc execution test

2006-10-30 Thread ebotcazou at gcc dot gnu dot org
--- Comment #11 from ebotcazou at gcc dot gnu dot org 2006-10-30 14:50 --- Investigating. -- ebotcazou at gcc dot gnu dot org changed: What|Removed |Added

[Bug target/29639] FAIL: ext/bitmap_allocator/check_allocate_max_size.cc execution test

2006-10-29 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-10-30 00:02 --- http://gcc.gnu.org/ml/gcc-patches/2004-04/msg01768.html Hmm, I bet this is really a binutils bug. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29639

[Bug target/29639] FAIL: ext/bitmap_allocator/check_allocate_max_size.cc execution test

2006-10-29 Thread pcarlini at suse dot de
--- Comment #2 from pcarlini at suse dot de 2006-10-30 00:08 --- (In reply to comment #1) http://gcc.gnu.org/ml/gcc-patches/2004-04/msg01768.html Are you sure this *2004* patch is relevant? Hmm, I bet this is really a binutils bug. I'm seeing the problem with a stock 2.17, if

[Bug target/29639] FAIL: ext/bitmap_allocator/check_allocate_max_size.cc execution test

2006-10-29 Thread pinskia at gcc dot gnu dot org
--- Comment #3 from pinskia at gcc dot gnu dot org 2006-10-30 00:21 --- (In reply to comment #2) (In reply to comment #1) http://gcc.gnu.org/ml/gcc-patches/2004-04/msg01768.html Are you sure this *2004* patch is relevant? Yes since it just went in during the time frame you

[Bug target/29639] FAIL: ext/bitmap_allocator/check_allocate_max_size.cc execution test

2006-10-29 Thread pcarlini at suse dot de
--- Comment #4 from pcarlini at suse dot de 2006-10-30 00:27 --- (In reply to comment #3) Are you sure this *2004* patch is relevant? Yes since it just went in during the time frame you mentioned: 2006-10-28 Eric Botcazou [EMAIL PROTECTED] Crazy. Ok, thanks, let's add Eric