From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Rong Xu <xur@google.com>
Cc: Andrew Pinski <pinskia@gmail.com>,
Richard Henderson <rth@redhat.com>,
Richard Biener <richard.guenther@gmail.com>,
Xinliang David Li <davidxl@google.com>,
Jan Hubicka <hubicka@ucw.cz>,
GCC Patches <gcc-patches@gcc.gnu.org>,
<reply@codereview.appspotmail.com>
Subject: Re: atomic update of profile counters (issue7000044)
Date: Wed, 20 Nov 2013 23:18:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1311202101470.4182@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAF1bQ=R_qgrDHRyOKNr0eaN9BFOWku4bR6tFJeSRz6hoSCrjqQ@mail.gmail.com>
On Wed, 20 Nov 2013, Rong Xu wrote:
> I could do this in the SPEC
> -Wl,-Bstatic -latomic -Wl,-Bdynamic
> which would link libatomic statically.
> I works for me. But it looks a little weird in gcc driver.
I think we should generally link libatomic with --as-needed by default on
platforms supporting --as-needed, in line with the general principle that
C code just using language not library facilities (_Atomic in this case)
shouldn't need any special options to link it (libatomic is like libgcc,
which is linked in automatically); the trickier question is what to do
with it on any systems supporting shared libraries but not --as-needed.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2013-11-20 21:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 6:45 Rong Xu
2012-12-21 9:25 ` Jan Hubicka
2012-12-21 18:38 ` Rong Xu
2012-12-28 19:33 ` Rong Xu
2012-12-28 19:35 ` Xinliang David Li
2013-01-03 1:16 ` Rong Xu
2013-01-03 1:25 ` Andrew Pinski
2013-01-03 1:29 ` Rong Xu
2013-01-03 1:31 ` Andrew Pinski
2013-01-03 9:05 ` Richard Biener
2013-01-04 0:42 ` Rong Xu
2013-01-07 20:36 ` Richard Henderson
2013-01-07 20:56 ` Rong Xu
2013-11-20 7:03 ` Rong Xu
2013-11-20 7:20 ` Andrew Pinski
2013-11-20 19:59 ` Rong Xu
2013-11-20 20:08 ` Andrew Pinski
2013-11-20 20:31 ` Andrew Pinski
2013-11-20 23:18 ` Joseph S. Myers [this message]
2013-11-21 0:07 ` Rong Xu
2013-11-21 0:14 ` Andrew Pinski
2013-11-21 1:24 ` Rong Xu
2014-05-26 6:01 ` Jan Hubicka
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=Pine.LNX.4.64.1311202101470.4182@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=davidxl@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=pinskia@gmail.com \
--cc=reply@codereview.appspotmail.com \
--cc=richard.guenther@gmail.com \
--cc=rth@redhat.com \
--cc=xur@google.com \
/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).