public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Hiroki Kaminaga <kaminaga@sm.sony.co.jp>
To: gcc-help@gcc.gnu.org, brian@dessent.net
Cc: kaminaga@sm.sony.co.jp
Subject: Re: -fpic vs fPIC
Date: Mon, 12 Jun 2006 03:30:00 -0000	[thread overview]
Message-ID: <20060612.122717.78704883.kaminaga@sm.sony.co.jp> (raw)
In-Reply-To: <448CD055.4A2C5D58@dessent.net>

> Hiroki Kaminaga wrote:
> 
> > What is the difference of -fpic and -fPIC?
> > Is there any info doc?
> 
> http://gcc.gnu.org/onlinedocs/gcc-4.1.1/gcc/Code-Gen-Options.html#index-fpic-1614

Thank you very much.

On ppc32/linux target, -fpic and -fPIC is available, and from the
above info, I assume -fpic is better for performance, and if library
GOT size exceeds 32k, -fPIC is the only chice.


(Hiroki Kaminaga)
--

  reply	other threads:[~2006-06-12  3:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-12  1:31 Hiroki Kaminaga
2006-06-12  2:24 ` Brian Dessent
2006-06-12  3:30   ` Hiroki Kaminaga [this message]
2006-06-12  3:40     ` Brian Dessent

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=20060612.122717.78704883.kaminaga@sm.sony.co.jp \
    --to=kaminaga@sm.sony.co.jp \
    --cc=brian@dessent.net \
    --cc=gcc-help@gcc.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).