public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
* [Bug libstdc++/31777] New: GLIBCXX_FORCE_NEW doesn't always work in pool_allocator
@ 2007-05-01 21:31 gcc at severeweblint dot org
2007-05-01 22:57 ` [Bug libstdc++/31777] " pcarlini at suse dot de
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: gcc at severeweblint dot org @ 2007-05-01 21:31 UTC (permalink / raw)
To: gcc-bugs
in revision 83355 of libstdc++-v3/include/ext/pool_allocator.h the efficient
thread support code for GLIBCXX_FORCE_NEW was broken by changing the test
(_S_force_new>0) to (_S_force_new==1). now there is a race condition.
--
Summary: GLIBCXX_FORCE_NEW doesn't always work in pool_allocator
Product: gcc
Version: 3.4.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: gcc at severeweblint dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31777
^ permalink raw reply [flat|nested] 5+ messages in thread* [Bug libstdc++/31777] GLIBCXX_FORCE_NEW doesn't always work in pool_allocator 2007-05-01 21:31 [Bug libstdc++/31777] New: GLIBCXX_FORCE_NEW doesn't always work in pool_allocator gcc at severeweblint dot org @ 2007-05-01 22:57 ` pcarlini at suse dot de 2007-05-01 23:02 ` pcarlini at suse dot de ` (2 subsequent siblings) 3 siblings, 0 replies; 5+ messages in thread From: pcarlini at suse dot de @ 2007-05-01 22:57 UTC (permalink / raw) To: gcc-bugs ------- Comment #1 from pcarlini at suse dot de 2007-05-01 23:57 ------- Gosh you are right, will fix it asap. Thanks. -- pcarlini at suse dot de changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |pcarlini at suse dot de |dot org | Status|UNCONFIRMED |ASSIGNED Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2007-05-01 23:57:05 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31777 ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug libstdc++/31777] GLIBCXX_FORCE_NEW doesn't always work in pool_allocator 2007-05-01 21:31 [Bug libstdc++/31777] New: GLIBCXX_FORCE_NEW doesn't always work in pool_allocator gcc at severeweblint dot org 2007-05-01 22:57 ` [Bug libstdc++/31777] " pcarlini at suse dot de @ 2007-05-01 23:02 ` pcarlini at suse dot de 2007-05-02 18:37 ` paolo at gcc dot gnu dot org 2007-05-20 8:27 ` pcarlini at suse dot de 3 siblings, 0 replies; 5+ messages in thread From: pcarlini at suse dot de @ 2007-05-01 23:02 UTC (permalink / raw) To: gcc-bugs -- pcarlini at suse dot de changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |4.2.1 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31777 ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug libstdc++/31777] GLIBCXX_FORCE_NEW doesn't always work in pool_allocator 2007-05-01 21:31 [Bug libstdc++/31777] New: GLIBCXX_FORCE_NEW doesn't always work in pool_allocator gcc at severeweblint dot org 2007-05-01 22:57 ` [Bug libstdc++/31777] " pcarlini at suse dot de 2007-05-01 23:02 ` pcarlini at suse dot de @ 2007-05-02 18:37 ` paolo at gcc dot gnu dot org 2007-05-20 8:27 ` pcarlini at suse dot de 3 siblings, 0 replies; 5+ messages in thread From: paolo at gcc dot gnu dot org @ 2007-05-02 18:37 UTC (permalink / raw) To: gcc-bugs ------- Comment #2 from paolo at gcc dot gnu dot org 2007-05-02 19:37 ------- Subject: Bug 31777 Author: paolo Date: Wed May 2 18:37:00 2007 New Revision: 124355 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=124355 Log: 2007-05-02 Paolo Carlini <pcarlini@suse.de> PR libstdc++/31777 * include/ext/pool_allocator.h (__pool_alloc<>::allocate, __pool_alloc<>::deallocate): Fix _S_force_new check. Modified: trunk/libstdc++-v3/ChangeLog trunk/libstdc++-v3/include/ext/pool_allocator.h -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31777 ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug libstdc++/31777] GLIBCXX_FORCE_NEW doesn't always work in pool_allocator 2007-05-01 21:31 [Bug libstdc++/31777] New: GLIBCXX_FORCE_NEW doesn't always work in pool_allocator gcc at severeweblint dot org ` (2 preceding siblings ...) 2007-05-02 18:37 ` paolo at gcc dot gnu dot org @ 2007-05-20 8:27 ` pcarlini at suse dot de 3 siblings, 0 replies; 5+ messages in thread From: pcarlini at suse dot de @ 2007-05-20 8:27 UTC (permalink / raw) To: gcc-bugs ------- Comment #3 from pcarlini at suse dot de 2007-05-20 09:26 ------- Better fixing in mainline only, only GLIBCXX_FORCE_NEW has problems (in an extension allocator) -- pcarlini at suse dot de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED Target Milestone|4.2.1 |4.3.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31777 ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2007-05-20 8:27 UTC | newest] Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2007-05-01 21:31 [Bug libstdc++/31777] New: GLIBCXX_FORCE_NEW doesn't always work in pool_allocator gcc at severeweblint dot org 2007-05-01 22:57 ` [Bug libstdc++/31777] " pcarlini at suse dot de 2007-05-01 23:02 ` pcarlini at suse dot de 2007-05-02 18:37 ` paolo at gcc dot gnu dot org 2007-05-20 8:27 ` pcarlini at suse dot de
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).