From: Andrew MacLeod <amacleod@redhat.com>
To: "gcc-patches@gnu.org" <gcc-patches@gnu.org>
Subject: revert patch
Date: Mon, 07 Nov 2011 21:45:00 -0000 [thread overview]
Message-ID: <4EB8501D.2040403@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 583 bytes --]
I had to revert a minor change in the last patch. It didn't show any
problems in an incremental bootstrap, but once from scratch showed a
compile failure due to a duplicate definition.
I'll have to fix the lack of an atomic_thread_fence or
atomic_signal_fence a different way apparently.
Sorry. If you encounter this, you'll have to touch
libstdc++-v3/src/*.cc in order to get the proper things rebuilt since
the dependency seems to be missing on atomic_base.h.
I'll add that in when I do the proper fix later. This will get everyone
back up and running.
Sorry
Andrew
[-- Attachment #2: P --]
[-- Type: text/plain, Size: 896 bytes --]
2011-11-07 Andrew MacLeod <amacleod@redhat.com>
* include/bits/atomic_base.h (atomic_thread_fence): Revert.
(atomic_signal_fence): Revert.
Index: include/bits/atomic_base.h
===================================================================
*** include/bits/atomic_base.h (revision 181118)
--- include/bits/atomic_base.h (revision 181119)
*************** _GLIBCXX_BEGIN_NAMESPACE_VERSION
*** 69,84 ****
}
void
! atomic_thread_fence(memory_order __m) noexcept
! {
! __atomic_thread_fence (__m);
! }
void
! atomic_signal_fence(memory_order __m) noexcept
! {
! __atomic_signal_fence (__m);
! }
/// kill_dependency
template<typename _Tp>
--- 69,78 ----
}
void
! atomic_thread_fence(memory_order __m) noexcept;
void
! atomic_signal_fence(memory_order __m) noexcept;
/// kill_dependency
template<typename _Tp>
reply other threads:[~2011-11-07 21:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4EB8501D.2040403@redhat.com \
--to=amacleod@redhat.com \
--cc=gcc-patches@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).