public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bkoz at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/40654] [C++0x] atomic.cc: 'd' is used uninitialized warning
Date: Sun, 18 Oct 2009 03:30:00 -0000	[thread overview]
Message-ID: <20091018033021.15007.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40654-17247@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from bkoz at gcc dot gnu dot org  2009-10-18 03:30 -------
Subject: Bug 40654

Author: bkoz
Date: Sun Oct 18 03:30:03 2009
New Revision: 152965

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=152965
Log:
2009-10-16  Benjamin Kosnik  <bkoz@redhat.com>

        * include/c_compatibility/stdatomic.h: Include cstdatomic if
        __cplusplus.

2009-10-15  Benjamin Kosnik  <bkoz@redhat.com>

        PR libstdc++/40654
        PR libstdc++/40826
        * src/atomic.cc (atomic_flag_test_and_set_explicit): Add
        static_cast from base to derived.
        (atomic_flag_clear_explicit): Same.
        * include/bits/atomic_2.h (__atomic2::atomic_flag): Public derivation.
        Remove value type constructor.
        * include/bits/atomic_0.h (__atomic0::atomic_flag): Same.
        * include/std/future (_Future_state): Use ATOMIC_FLAG_INIT to
        initialized the atomic_flag member.

Added:
   
branches/gcc-4_4-branch/libstdc++-v3/testsuite/29_atomics/atomic_flag/clear/
   
branches/gcc-4_4-branch/libstdc++-v3/testsuite/29_atomics/atomic_flag/clear/1.c
   
branches/gcc-4_4-branch/libstdc++-v3/testsuite/29_atomics/atomic_flag/clear/1.cc
   
branches/gcc-4_4-branch/libstdc++-v3/testsuite/29_atomics/atomic_flag/cons/1.cc
Modified:
    branches/gcc-4_4-branch/libstdc++-v3/ChangeLog
    branches/gcc-4_4-branch/libstdc++-v3/include/bits/atomic_0.h
    branches/gcc-4_4-branch/libstdc++-v3/include/bits/atomic_2.h
    branches/gcc-4_4-branch/libstdc++-v3/include/c_compatibility/stdatomic.h
    branches/gcc-4_4-branch/libstdc++-v3/src/atomic.cc


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40654


  parent reply	other threads:[~2009-10-18  3:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-05 14:39 [Bug libstdc++/40654] New: " sezeroz at gmail dot com
2009-07-05 18:09 ` [Bug libstdc++/40654] " paolo dot carlini at oracle dot com
2009-07-06 23:55 ` bkoz at gcc dot gnu dot org
2009-07-22 14:29 ` [Bug libstdc++/40654] [C++0x] " paolo dot carlini at oracle dot com
2009-10-16  7:48 ` bkoz at gcc dot gnu dot org
2009-10-16 19:49 ` sezeroz at gmail dot com
2009-10-18  3:30 ` bkoz at gcc dot gnu dot org [this message]
2009-10-19 16:46 ` bkoz at gcc dot gnu dot 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=20091018033021.15007.qmail@sourceware.org \
    --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).