public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/51296] Several 30_threads tests FAIL on Tru64 UNIX
Date: Fri, 25 Nov 2011 15:21:00 -0000 [thread overview]
Message-ID: <bug-51296-4-d9OzZWiFfe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51296-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51296
--- Comment #9 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2011-11-25 14:57:24 UTC ---
> --- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-11-25 14:46:07 UTC ---
> Thanks for the info - that error implies the mutex was not correctly
> initialized.
>
> What are these macros defined to (if defined)?
>
> __GTHREAD_MUTEX_INIT
> __GTHREAD_MUTEX_INIT
> __GTHREAD_MUTEX_INIT_FUNCTION
With -g3 -save-temps, I find
#define __GTHREAD_MUTEX_INIT PTHREAD_MUTEX_INITIALIZER
and
#define PTHREAD_MUTEX_INITIALIZER {_PTHREAD_MSTATE_CONFIG, _PTHREAD_MVALID |
_PTHREAD_MVF_STA}
#define _PTHREAD_MSTATE_CONFIG 0x00200000
#define _PTHREAD_MVALID (0x05bcafe1L)
#define _PTHREAD_MVF_STA 0x08000000L
>> FAIL: 30_threads/future/cons/constexpr.cc scan-assembler-not
> _ZNSt6futureIvEC2Ev
>> FAIL: 30_threads/future/cons/constexpr.cc scan-assembler-not
> _ZNSt6futureIiEC2Ev
>> FAIL: 30_threads/shared_future/cons/constexpr.cc scan-assembler-not
> _ZNSt13shared_futureIvEC2Ev
>> FAIL: 30_threads/shared_future/cons/constexpr.cc scan-assembler-not
> _ZNSt13shared_futureIiEC2Ev
>
> These errors indicate a front-end problem (failing to do static init for the
> constexpr constructor) or a bug in the testcase.
I think it's a testcase bug: for the first case, grep reveals
#.stabs "future:Tt4100=s16!1,020,4071;__base_ctor
::4102=#4100,3,4103=*4100,4104=&4105=k4106=4072,3;:_ZNSt6futureIvEC2ERKSt10shared_ptrINSt13__future_base11_State_baseEE;0A.;__comp_ctor
::4102:_ZNSt6futureIvEC1ERKSt10shared_ptrINSt13__future_base11_State_baseEE;0A.;__base_ctor
::4107=#4100,3,4103,3;:_ZNSt6futureIvEC2Ev;2A.;__comp_ctor
::4107:_ZNSt6futureIvEC1Ev;2A.;__base_ctor
::4108=#4100,3,4103,4109=&4110=4100,3;:_ZNSt6futureIvEC2EOS0_;2A.;__comp_ctor
::4108:_ZNSt6futureIvEC1EOS0_;2A.;__base_ctor
::4111=#4100,3,4103,4112=&4113=k4110,3;:_ZNSt6futureIvEC2ERKS0_;2A.;__comp_ctor
::4111:_ZNSt6futureIvEC1ERKS0_;2A.;operator=::4114=#4100,4115=&4110,4103,4112,3;:_ZNSt6futureIvEaSERKS0_;2A.4116=#4100,4115,4103,4109,3;:_ZNSt6futureIvEaSEOS0_;2A.;get::4117=#4100,3,4103,3;:_ZNSt6futureIvE3getEv;2A.;share::4118=#4100,4095,4103,3;:_ZNSt6futureIvE5shareEv;2A.;;",128,0,727,0
With -g0, grep finds nothing else.
Rainer
next prev parent reply other threads:[~2011-11-25 14:58 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 18:08 [Bug libstdc++/51296] New: " ro at gcc dot gnu.org
2011-11-24 19:27 ` [Bug libstdc++/51296] " redi at gcc dot gnu.org
2011-11-24 20:30 ` redi at gcc dot gnu.org
2011-11-24 21:37 ` redi at gcc dot gnu.org
2011-11-25 14:13 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-11-25 14:36 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-11-25 14:47 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-11-25 15:17 ` redi at gcc dot gnu.org
2011-11-25 15:18 ` redi at gcc dot gnu.org
2011-11-25 15:21 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2011-11-25 15:22 ` redi at gcc dot gnu.org
2011-11-25 16:26 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-11-26 15:24 ` redi at gcc dot gnu.org
2011-11-26 16:03 ` redi at gcc dot gnu.org
2011-11-28 13:24 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-11-28 14:35 ` redi at gcc dot gnu.org
2011-11-28 14:40 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-11-28 15:10 ` redi at gcc dot gnu.org
2012-01-11 16:50 ` redi at gcc dot gnu.org
2012-01-11 17:38 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-01-11 17:49 ` redi at gcc dot gnu.org
2012-01-12 15:48 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-01-12 16:16 ` redi at gcc dot gnu.org
2012-01-12 18:18 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-01-13 10:34 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-01-13 10:54 ` redi at gcc dot gnu.org
2012-01-16 19:37 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-01-16 19:52 ` redi at gcc dot gnu.org
2012-01-31 12:48 ` ro at gcc dot gnu.org
2012-01-31 20:04 ` redi at gcc dot gnu.org
2012-02-01 10:24 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-02-01 10:59 ` redi at gcc dot gnu.org
2012-02-03 8:50 ` redi at gcc dot gnu.org
2012-02-03 8:52 ` redi at gcc dot gnu.org
2012-02-03 9:48 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-02-03 9:51 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-02-07 9:20 ` redi at gcc dot gnu.org
2012-02-07 9:23 ` redi at gcc dot gnu.org
2012-02-10 17:01 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-02-10 18:11 ` ro at gcc dot gnu.org
2012-02-10 18:14 ` ro at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-51296-4-d9OzZWiFfe@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).