This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [semi PATCH] ARM/Thumb branches out of range for MI thunks
- From: Richard Earnshaw <rearnsha at arm dot com>
- To: "Zack Weinberg" <zack at codesourcery dot com>
- Cc: Richard dot Earnshaw at arm dot com, Daniel Jacobowitz <drow at mvista dot com>, Phil Edwards <phil at codesourcery dot com>, gcc-patches at gcc dot gnu dot org, rearnsha at arm dot com
- Date: Sat, 25 Oct 2003 09:56:16 +0100
- Subject: Re: [semi PATCH] ARM/Thumb branches out of range for MI thunks
- Organization: ARM Ltd.
- Reply-to: Richard dot Earnshaw at arm dot com
> Ok, so it seems clear that we ought to emit these thunks in ARM mode.
> It also seems clear that including C++ front end headers in arm.c is
> not the right way to do it.
>
> Richard, what do you think the right way would be? What information
> needs to get exposed in a language-independent manner, so that the
> ARM back end can do the right thing?
I discussed this briefly in private mail with Mark, and his suggestion was
to implement thunks for the vcall offset case as well. Once that is done
we can eliminate the dependence on THUNK_VCALL_OFFSET in arm.c and the
whole interface becomes much cleaner, since we can just depend on the
current_function_is_thunk.
I currently don't have time to look into this myself, and I know very
little about the front ends in any case.
R.