* [Bug libstdc++/21842] [4.1 Regression] 23_containers/bitset/operations/2.cc execution test fails
2005-05-31 16:36 [Bug libstdc++/21842] New: [4.1 Regression] 23_containers/bitset/operations/2.cc execution test fails jsm28 at gcc dot gnu dot org
@ 2005-05-31 16:49 ` pcarlini at suse dot de
2005-05-31 16:51 ` [Bug middle-end/21842] " pinskia at gcc dot gnu dot org
` (7 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: pcarlini at suse dot de @ 2005-05-31 16:49 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From pcarlini at suse dot de 2005-05-31 16:49 -------
Notice that *nothing* changed in the relevant libstdc++-v3 code. Generally, only
small, confined changes lately. Either this is a miscompilation or a *very* long
standing latent problem. Can you attach the *.log excerpt? Even better, take care
of the obvious checks, like compiling at lower optimization level? (I'm also
going to do that, anyway: we want to ascertain the miscompilation and recategorize
as soon as possible, in case)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21842
^ permalink raw reply [flat|nested] 10+ messages in thread* [Bug middle-end/21842] [4.1 Regression] 23_containers/bitset/operations/2.cc execution test fails
2005-05-31 16:36 [Bug libstdc++/21842] New: [4.1 Regression] 23_containers/bitset/operations/2.cc execution test fails jsm28 at gcc dot gnu dot org
2005-05-31 16:49 ` [Bug libstdc++/21842] " pcarlini at suse dot de
@ 2005-05-31 16:51 ` pinskia at gcc dot gnu dot org
2005-05-31 17:01 ` pcarlini at suse dot de
` (6 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2005-05-31 16:51 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-31 16:50 -------
I want to say the same patch which broke 920501-2.c also broke this.
--
What |Removed |Added
----------------------------------------------------------------------------
BugsThisDependsOn| |21843
Component|libstdc++ |middle-end
Keywords| |wrong-code
Target Milestone|--- |4.1.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21842
^ permalink raw reply [flat|nested] 10+ messages in thread* [Bug middle-end/21842] [4.1 Regression] 23_containers/bitset/operations/2.cc execution test fails
2005-05-31 16:36 [Bug libstdc++/21842] New: [4.1 Regression] 23_containers/bitset/operations/2.cc execution test fails jsm28 at gcc dot gnu dot org
2005-05-31 16:49 ` [Bug libstdc++/21842] " pcarlini at suse dot de
2005-05-31 16:51 ` [Bug middle-end/21842] " pinskia at gcc dot gnu dot org
@ 2005-05-31 17:01 ` pcarlini at suse dot de
2005-05-31 17:06 ` joseph at codesourcery dot com
` (5 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: pcarlini at suse dot de @ 2005-05-31 17:01 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From pcarlini at suse dot de 2005-05-31 16:59 -------
... well, at least both involve shifts ;)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21842
^ permalink raw reply [flat|nested] 10+ messages in thread* [Bug middle-end/21842] [4.1 Regression] 23_containers/bitset/operations/2.cc execution test fails
2005-05-31 16:36 [Bug libstdc++/21842] New: [4.1 Regression] 23_containers/bitset/operations/2.cc execution test fails jsm28 at gcc dot gnu dot org
` (2 preceding siblings ...)
2005-05-31 17:01 ` pcarlini at suse dot de
@ 2005-05-31 17:06 ` joseph at codesourcery dot com
2005-05-31 17:15 ` pcarlini at suse dot de
` (4 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: joseph at codesourcery dot com @ 2005-05-31 17:06 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From joseph at codesourcery dot com 2005-05-31 17:05 -------
Subject: Re: [4.1 Regression] 23_containers/bitset/operations/2.cc
execution test fails
On Tue, 31 May 2005, pcarlini at suse dot de wrote:
> Notice that *nothing* changed in the relevant libstdc++-v3 code. Generally, only
> small, confined changes lately. Either this is a miscompilation or a *very* long
> standing latent problem. Can you attach the *.log excerpt? Even better, take care
> of the obvious checks, like compiling at lower optimization level? (I'm also
> going to do that, anyway: we want to ascertain the miscompilation and recategorize
> as soon as possible, in case)
Executing on host: g++ -g -O2 -D_GLIBCXX_ASSERT -fmessage-length=0
-DLOCALEDIR="/scratch/gcc/nightly-2005-05-31-mainline/i686-pc-linux-gnu/build_gcc/install/bin/../share/locale"
-I/home/gcc/nightlies/src-mainline-2005-05-31/gcc-mainline/libstdc++-v3/testsuite
testsuite_abi.o testsuite_allocator.o testsuite_character.o
testsuite_hooks.o
/home/gcc/nightlies/src-mainline-2005-05-31/gcc-mainline/libstdc++-v3/testsuite/23_containers/bitset/operations/2.cc
-include bits/stdc++.h -lm -o ./2.exe (timeout = 300)
PASS: 23_containers/bitset/operations/2.cc (test for excess errors)
Setting LD_LIBRARY_PATH to
:/scratch/gcc/nightly-2005-05-31-mainline/i686-pc-linux-gnu/build_gcc/install/lib:/usr/local/tools/gcc-3.4.0/lib
2.exe:
/home/gcc/nightlies/src-mainline-2005-05-31/gcc-mainline/libstdc++-v3/testsuite/23_containers/bitset/operations/2.cc:33:
bool test02(): Assertion `b.count() == 0' failed.
FAIL: 23_containers/bitset/operations/2.cc execution test
(this is installed compiler testing, hence the short command line).
Testing manually it seems to fail with -O2 or -O but not -O0.
In general when reporting bugs shown up by my regression tester I don't
know what part of the compiler they are in; I check enough to make sure
they don't appear to be system problems and aren't already reported with
reference to the named testcase or discussed on the lists as fixed, but
not to determine the exact cause.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21842
^ permalink raw reply [flat|nested] 10+ messages in thread* [Bug middle-end/21842] [4.1 Regression] 23_containers/bitset/operations/2.cc execution test fails
2005-05-31 16:36 [Bug libstdc++/21842] New: [4.1 Regression] 23_containers/bitset/operations/2.cc execution test fails jsm28 at gcc dot gnu dot org
` (3 preceding siblings ...)
2005-05-31 17:06 ` joseph at codesourcery dot com
@ 2005-05-31 17:15 ` pcarlini at suse dot de
2005-05-31 17:49 ` joseph at codesourcery dot com
` (3 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: pcarlini at suse dot de @ 2005-05-31 17:15 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From pcarlini at suse dot de 2005-05-31 17:14 -------
> Testing manually it seems to fail with -O2 or -O but not -O0.
Ah, ah, the same happens for the other regression that you just filed, it
seems! Thanks.
> In general when reporting bugs shown up by my regression tester I don't
> know what part of the compiler they are in; I check enough to make sure
> they don't appear to be system problems and aren't already reported with
> reference to the named testcase or discussed on the lists as fixed, but
> not to determine the exact cause.
Ok, this is by itself absolutely useful, of course. Only, categorizing as
libstdc++-v3 can be "distracting", you know what I mean? Luckily, we have
our trusty "bug masters" to take care of that ;)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21842
^ permalink raw reply [flat|nested] 10+ messages in thread* [Bug middle-end/21842] [4.1 Regression] 23_containers/bitset/operations/2.cc execution test fails
2005-05-31 16:36 [Bug libstdc++/21842] New: [4.1 Regression] 23_containers/bitset/operations/2.cc execution test fails jsm28 at gcc dot gnu dot org
` (4 preceding siblings ...)
2005-05-31 17:15 ` pcarlini at suse dot de
@ 2005-05-31 17:49 ` joseph at codesourcery dot com
2005-05-31 17:56 ` pinskia at gcc dot gnu dot org
` (2 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: joseph at codesourcery dot com @ 2005-05-31 17:49 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From joseph at codesourcery dot com 2005-05-31 17:46 -------
Subject: Re: [4.1 Regression] 23_containers/bitset/operations/2.cc
execution test fails
On Tue, 31 May 2005, pcarlini at suse dot de wrote:
> Ok, this is by itself absolutely useful, of course. Only, categorizing as
> libstdc++-v3 can be "distracting", you know what I mean? Luckily, we have
> our trusty "bug masters" to take care of that ;)
Indeed, I leave it to the bugmasters to decide if there's a component
which is a better approximation, or that the bug is the same as another
one not mentioning the testcase in question, or is an issue fixed without
mentioning the testcase. Where the bug doesn't happen on i686-linux I may
in due course run a binary search to identify the responsible patch.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21842
^ permalink raw reply [flat|nested] 10+ messages in thread* [Bug middle-end/21842] [4.1 Regression] 23_containers/bitset/operations/2.cc execution test fails
2005-05-31 16:36 [Bug libstdc++/21842] New: [4.1 Regression] 23_containers/bitset/operations/2.cc execution test fails jsm28 at gcc dot gnu dot org
` (5 preceding siblings ...)
2005-05-31 17:49 ` joseph at codesourcery dot com
@ 2005-05-31 17:56 ` pinskia at gcc dot gnu dot org
2005-06-01 17:53 ` jsm28 at gcc dot gnu dot org
2005-06-01 17:54 ` jsm28 at gcc dot gnu dot org
8 siblings, 0 replies; 10+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2005-05-31 17:56 UTC (permalink / raw)
To: gcc-bugs
--
What |Removed |Added
----------------------------------------------------------------------------
GCC target triplet| |i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21842
^ permalink raw reply [flat|nested] 10+ messages in thread* [Bug middle-end/21842] [4.1 Regression] 23_containers/bitset/operations/2.cc execution test fails
2005-05-31 16:36 [Bug libstdc++/21842] New: [4.1 Regression] 23_containers/bitset/operations/2.cc execution test fails jsm28 at gcc dot gnu dot org
` (6 preceding siblings ...)
2005-05-31 17:56 ` pinskia at gcc dot gnu dot org
@ 2005-06-01 17:53 ` jsm28 at gcc dot gnu dot org
2005-06-01 17:54 ` jsm28 at gcc dot gnu dot org
8 siblings, 0 replies; 10+ messages in thread
From: jsm28 at gcc dot gnu dot org @ 2005-06-01 17:53 UTC (permalink / raw)
To: gcc-bugs
------- Additional Comments From jsm28 at gcc dot gnu dot org 2005-06-01 17:53 -------
Fixed mainline 20050601.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21842
^ permalink raw reply [flat|nested] 10+ messages in thread* [Bug middle-end/21842] [4.1 Regression] 23_containers/bitset/operations/2.cc execution test fails
2005-05-31 16:36 [Bug libstdc++/21842] New: [4.1 Regression] 23_containers/bitset/operations/2.cc execution test fails jsm28 at gcc dot gnu dot org
` (7 preceding siblings ...)
2005-06-01 17:53 ` jsm28 at gcc dot gnu dot org
@ 2005-06-01 17:54 ` jsm28 at gcc dot gnu dot org
8 siblings, 0 replies; 10+ messages in thread
From: jsm28 at gcc dot gnu dot org @ 2005-06-01 17:54 UTC (permalink / raw)
To: gcc-bugs
--
Bug 21842 depends on bug 21843, which changed state.
Bug 21843 Summary: [4.1 Regression] gcc.c-torture/execute/920501-2.c execution fails
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21843
What |Old Value |New Value
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21842
^ permalink raw reply [flat|nested] 10+ messages in thread