This is the mail archive of the
mailing list for the GCC project.
Re: interest for ARM/thumb multiversionning ?
- From: Ramana Radhakrishnan <ramana dot radhakrishnan at foss dot arm dot com>
- To: Christian Bruel <christian dot bruel at st dot com>, Richard Earnshaw <Richard dot Earnshaw at arm dot com>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Wed, 29 Apr 2015 16:36:52 +0100
- Subject: Re: interest for ARM/thumb multiversionning ?
- Authentication-results: sourceware.org; auth=none
- References: <55409559 dot 1010707 at st dot com>
On 29/04/2015 09:24, Christian Bruel wrote:
Hi Ramana, Richard
After playing with the attritute ((target ("[thumb,arm]")), during the
pending review, I added the "default" selector to neutralize
-mflip-thumb for the setjmp/longjmp based tests.
I was wondering it there would be an interest leverage on this to
implement multiprocessing, like on the x86 ?
You mean multiversioning ? How would the dispatcher work in this case ?
something that would allow (from the x86 doc)
__attribute__ ((target ("default")))
int foo ()
__attribute__ ((target ("thumb")))
int foo ()
int main ()
int (*p)() = &foo;
assert ((*p) () == foo ());
I had initially not planned to do it, but this is a simple extension of
the attribute target, if someone find a use for this I can implement it
on the fly.