From: Ian Lance Taylor <iant@google.com>
To: Kevin Klues <klueska@cs.berkeley.edu>
Cc: gcc-help@gcc.gnu.org
Subject: Re: TLS, gcc optimizations, and PIC on x86
Date: Tue, 06 Sep 2011 07:10:00 -0000 [thread overview]
Message-ID: <mcr1uvuxi2p.fsf@coign.corp.google.com> (raw)
In-Reply-To: <CAJR1fVotbJvjOx-y6iEoobOj_Q+-sjM-cJeFfPk5cDbNf1xDig@mail.gmail.com> (Kevin Klues's message of "Thu, 1 Sep 2011 00:15:23 -0700")
Kevin Klues <klueska@cs.berkeley.edu> writes:
> That said, do you see any obvious issues with my solution? It seems
> to work for all of the test cases I've thrown at it, but I could be
> missing something. Additionally, do you have any suggestions for a
> better method that achieves similar results? Ideally I'd like a
> solution that didn't require the use of the 'optimize' attribute as
> (unfortunately) some of the systems on which we'd like to compile our
> code still use gcc < 4.4.
I don't see any obvious issues with your solution. I'm not sure why you
need to use the optimize attribute; I would have expected that the
noinline attribute would be sufficient here.
Ian
next prev parent reply other threads:[~2011-09-06 7:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 1:55 Kevin Klues
2011-09-01 5:01 ` Ian Lance Taylor
2011-09-01 7:15 ` Kevin Klues
2011-09-06 7:10 ` Ian Lance Taylor [this message]
2011-09-06 20:31 ` Kevin Klues
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=mcr1uvuxi2p.fsf@coign.corp.google.com \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=klueska@cs.berkeley.edu \
/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).