From: Ian Lance Taylor <iant@google.com>
To: Eli Bendersky <eliben@gmail.com>
Cc: gcc-help@gnu.org
Subject: Re: why does -fno-pic coge generation on x64 require the large model?
Date: Mon, 07 Nov 2011 18:12:00 -0000 [thread overview]
Message-ID: <mcrlirr7qf2.fsf@dhcp-172-18-216-180.mtv.corp.google.com> (raw)
In-Reply-To: <CAF-Rda9wwwSqwFpuCkT8f-HnPeTJ4tz=Mt5eBgR0DwV-7R0kwA@mail.gmail.com> (Eli Bendersky's message of "Mon, 7 Nov 2011 17:56:26 +0200")
Eli Bendersky <eliben@gmail.com> writes:
> What I'm trying to see is how to convince GCC to generate NON-PIC code
> and link it into a shared library for x64. I only managed to do this
> with "-fno-PIC -mcmodel=large", and I wonder why with other memory
> models it doesn't work out. I suspect this has to do with some
> artifact of x64's addressing modes for symbol offsets.
Yes. If it were easy to permit non-PIC x86_64 code in a shared library,
gcc would do it. But the only way to do that is, as you say, to use the
large memory model, which is relatively inefficient.
Ian
next prev parent reply other threads:[~2011-11-07 18:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 11:39 Eli Bendersky
2011-11-07 15:37 ` Ian Lance Taylor
2011-11-07 15:57 ` Eli Bendersky
2011-11-07 17:17 ` Andrew Haley
2011-11-07 18:12 ` Ian Lance Taylor [this message]
2011-11-08 3:19 ` Eli Bendersky
2011-11-08 5:49 ` Ian Lance Taylor
2011-11-08 6:09 ` Eli Bendersky
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=mcrlirr7qf2.fsf@dhcp-172-18-216-180.mtv.corp.google.com \
--to=iant@google.com \
--cc=eliben@gmail.com \
--cc=gcc-help@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).