From: Ian Lance Taylor <iant@google.com>
To: Richard Henderson <rth@redhat.com>
Cc: Matthias Klose <doko@ubuntu.com>,
Andreas Schwab <schwab@linux-m68k.org>,
gcc-patches@gcc.gnu.org
Subject: Re: PATCH RFA: PR go/55201: Create libatomic convenience library
Date: Tue, 18 Dec 2012 22:52:00 -0000 [thread overview]
Message-ID: <CAKOQZ8yamoyOOy0xe1MmzpmAEsAbbYyqbPVvmUnX601ix_we3g@mail.gmail.com> (raw)
In-Reply-To: <50D0EE7E.6000702@redhat.com>
On Tue, Dec 18, 2012 at 2:30 PM, Richard Henderson <rth@redhat.com> wrote:
> On 12/18/2012 02:09 PM, Ian Lance Taylor wrote:
>> I have now committed this follow-on patch, to make libgo use the new
>> libatomic_convenience library. This means that the changes to
>> explicitly link against -latomic are no longer necessary.
>
> Hang on, what are we doing here. Are we linking libatomic statically
> into libgo? That's only going to work so long as the target does not
> require the use of a mutex. While that's most desktop targets, it's
> certainly not all of them.
>
> If the target requires a mutex for the atomic operation, then there
> must be exactly one copy of the atomic library.
Argh. But why? Wouldn't that only apply to cases where the lock was
sometimes locked by one library and sometimes locked by a different
one?
Ian
next prev parent reply other threads:[~2012-12-18 22:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 19:30 Ian Lance Taylor
2012-12-18 21:32 ` Richard Henderson
2012-12-18 22:09 ` Ian Lance Taylor
2012-12-18 22:31 ` Richard Henderson
2012-12-18 22:52 ` Ian Lance Taylor [this message]
2012-12-18 23:09 ` Richard Henderson
2012-12-18 23:15 ` Richard Henderson
2012-12-19 0:28 ` Ian Lance Taylor
2012-12-19 15:38 ` Matthias Klose
2012-12-19 15:47 ` Ian Lance Taylor
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=CAKOQZ8yamoyOOy0xe1MmzpmAEsAbbYyqbPVvmUnX601ix_we3g@mail.gmail.com \
--to=iant@google.com \
--cc=doko@ubuntu.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rth@redhat.com \
--cc=schwab@linux-m68k.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).