This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: gcc-4.3.0 and -fPIC flags fails?

From: Brian Dessent <brian at dessent dot net>
To: "Franzi Edo." <edo dot franzi at ukos dot ch>
Cc: crossgcc at sourceware dot org
Date: Sun, 23 Mar 2008 10:35:23 -0700
Subject: Re: gcc-4.3.0 and -fPIC flags fails?
References: <ADFD8A9D-E000-4ACE-B3B3-03B64D8EBF08@ukos.ch>
Reply-to: crossgcc at sourceware dot org

"Franzi Edo." wrote:

> Unfortunately, the analysis of the routine __fixunssfsi, shows that some
> absolute calls remains (a couple of jsr !!!!). In the previous version
> of gcc (4.2.3)

Are you linking with static or shared libgcc?  That function is in
libgcc and if you link to a libgcc that wasn't built PIC then it follows
that it will have absolute addressing.

What target is this?  If you want you can probably change the multilib
options to specify that libgcc should be built -fPIC when static.  It
looks like OpenBSD does this already, see config/m68k/t-*.

Brian

--
For unsubscribe information see http://sourceware.org/lists.html#faq

References:
- gcc-4.3.0 and -fPIC flags fails?
  - From: Franzi Edo.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]