This is the mail archive of the crossgcc@sources.redhat.com 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: How to control location of startup code?

From: Richard Earnshaw <rearnsha at arm dot com>
To: Toralf Lund <toralf at procaptura dot com>
Cc: Richard Earnshaw <rearnsha at arm dot com>, crossgcc <crossgcc at sources dot redhat dot com>
Date: Wed, 31 Mar 2004 15:54:16 +0100
Subject: Re: How to control location of startup code?
Organization: ARM Ltd.
Reply-to: Richard Earnshaw <rearnsha at arm dot com>

> >>> .vectors           : { vectors.o(.vectors)  }
> >
> The problem is that as far as I can tell, this does not work for crt0.o, 
> at least not when implicitly loading the default one. In other words,
> 
> .vectors : { crt0.o(.vectors) }
> 
> doesn't work.
> 

I have to admit that I've not tried it myself.  However, if you have some 
behaviour that you think is incorrect, and you have a simple example that 
demonstrates this, then your best bet is to post a bug report on the 
binutils list.

R.


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com

References:
- Re: How to control location of startup code?
  - From: Toralf Lund

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