This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

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: ARM thumb interworking hole?

From: Ian Lance Taylor <ian at airs dot com>
To: manningc2 at actrix dot gen dot nz
Cc: Richard Earnshaw <rearnsha at gcc dot gnu dot org>, gcc at gcc dot gnu dot org
Date: 13 Jan 2005 13:16:52 -0500
Subject: Re: ARM thumb interworking hole?
References: <20050110060158.0ED854265@blood.actrix.co.nz><20050112233005.9C08616696@desire.actrix.co.nz><m3ekgqnrkj.fsf@gossamer.airs.com><20050113173722.9ECB71566B@desire.actrix.co.nz>

Charles Manning <manningc2@actrix.gen.nz> writes:

> On many devices you have memory areas that are more than 4MB apart and 
> therefore cannot be spanned with a branch. Currently gcc does not handle the 
> case of doing a long call to the interwork_call_via_rx code. THis means that 
> it is currently impossible to use Thumb with some device memory maps.

I do understand this.  As Richard said, and I agreed, this is best
fixed in the linker.

> "Upgrade to an ARMv5" is not at all a realistic way of thinking.

OK.  All the processors I've worked with myself do support ARMv5.

Ian

References:
- ARM thumb interworking hole?
  - From: Charles Manning
- Re: ARM thumb interworking hole?
  - From: Charles Manning
- Re: ARM thumb interworking hole?
  - From: Ian Lance Taylor
- Re: ARM thumb interworking hole?
  - From: Charles Manning

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