From: Johan Alfredsson <sduvan.gcc@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Compiling for single-threaded use (implicit threading support difference in 4.9.1 vs. 4.8.1)
Date: Thu, 16 Oct 2014 17:51:00 -0000 [thread overview]
Message-ID: <CA+pZiO7qV5oxHG2SsYTs75f0Ya_+orS0VTF=_kYxC+aCzAJ-zw@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdRhCQ3iyUVzcM1P+v_ypU=UBohTzBs+UF1RComTQPx50Q@mail.gmail.com>
On Thu, Oct 16, 2014 at 12:06 PM, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> On 16 October 2014 15:43, Johan Alfredsson wrote:
>> Sorry, my mistake. It turned out that librt was implicitly linked in
>> in the 4.9.1 case. However, the only things I use from librt are high
>> precision timers, so a switch to ensure no performance hit in my own
>> code would be great.
>
> Which suggests you were using --enable-libstdcxx-time=rt and so were
> not using the same configuration for both compilers.
No, this was something that happened due to the configuration of our
in-house build system. As I said, the configuration of the compilers
were identical.
> If you had told us the actual configurations for both versions that
> would have been obvious!
I did, and that was not the issue here.
> As Marc says, use a newer glibc to get high-precision timers without
> needing librt.
I'll look into that.
Thanks,
/Johan
next prev parent reply other threads:[~2014-10-16 17:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+pZiO6XXzJ7y-qu_F167ruqRwvZc8Sxnj4EAH2rXZwiODPbyw@mail.gmail.com>
2014-10-14 17:29 ` Fwd: " Johan Alfredsson
2014-10-15 9:14 ` Jonathan Wakely
2014-10-15 10:44 ` Jonathan Wakely
2014-10-16 14:43 ` Johan Alfredsson
2014-10-16 15:01 ` Marc Glisse
2014-10-16 16:06 ` Jonathan Wakely
2014-10-16 17:51 ` Johan Alfredsson [this message]
2014-10-15 11:40 ` Marc Glisse
2014-10-15 23:15 ` leon zadorin
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='CA+pZiO7qV5oxHG2SsYTs75f0Ya_+orS0VTF=_kYxC+aCzAJ-zw@mail.gmail.com' \
--to=sduvan.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.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).