RE: [Linux-ia64] [Patch] trivial fix in linker script

From: Siddha, Suresh B <>
Date: 2003-01-30 05:30:52
hi David,

I think you are mentioning about ret_from_clone patch here. 

I am using GNU linker. 

Inline with your observation, Intel compiler emits the type of extern variables. And now based on the order in which object files are linked, linker is failing in some cases. 

If the object file with extern declaration comes after the object file with correct declaration, linker is working fine. But if the object file with extern declaration comes first, then linker is reporting "type of symbol changed" in the second object file with correct declaration.

gcc doesn't fix the type for extern variables, leaves it to the linker. So linking works irrespective of the order.

Is this a GNU linker issue?


> -----Original Message-----
> From: David Mosberger []
> Sent: Tuesday, January 28, 2003 11:15 AM
> To: Siddha, Suresh B
> Cc:
> Subject: RE: [Linux-ia64] [Patch] trivial fix in linker script
> >>>>> On Fri, 24 Jan 2003 12:05:35 -0800, "Siddha, Suresh B" 
> <> said:
>   Suresh> hi David, I agree. Attached a bigger patch now :)
> Well, it's not pretty so I deferred working on it to the last, and
> then I got distracted and forgot to do something about it.
> Where exactly does the problem come from?  Is it that the Intel linker
> will complain when it finds the same symbol with different types?
> This kind of overzealous checking is quite a pain and is, IMHO, pretty
> much a bug (there are other annoying "features" like that in the Intel
> toolchain, for example that the assembler insists on all external
> symbols being declared; what a pain...).  If we need to have a
> workaround, we can add one but we should clearly document why the ugly
> hacks are needed.
> 	--david
> _______________________________________________
> Linux-IA64 mailing list
Received on Wed Jan 29 10:31:00 2003

This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:11 EST