This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/6123] __pic__/__PIC__ not defined when -fpic/-fPIC is specified
- From: "amodra at bigpond dot net dot au" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 10 Nov 2004 05:13:30 -0000
- Subject: [Bug target/6123] __pic__/__PIC__ not defined when -fpic/-fPIC is specified
- References: <20020401103600.6123.ghazi@caip.rutgers.edu>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From amodra at bigpond dot net dot au 2004-11-10 05:13 -------
No, actually not the next day, but a few days later. Incidentally, the (a) and
(b) are from an earlier reply of mine on this subject:
On most other targets, -fpic, ie. flag_pic, means two things:
a) generate PIC code, and
b) generate code suitable for ELF shared libraries.
I'll not argue the wisdom of -fpic meaning two things, but that's just
how things evolved. On PowerPC64, code generation is always PIC, but we
don't want the overhead of meeting shared library run-time symbol
resolution requirements when generating application code. Thus, we
don't want to set flag_pic all the time.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=6123