From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] sane-toolchain.inc: THUMB_INTERWORK should not be defined for armv4 and add armv4 to ARM EABI supporting architectures.
Date: Mon, 19 Jul 2010 09:29:41 -0700 [thread overview]
Message-ID: <AANLkTikuwarIRXUIOX1L2A2LBD7D-Rhglsd-Rur8QaOO@mail.gmail.com> (raw)
In-Reply-To: <1279549587.2345.2154.camel@mill.internal.reciva.com>
On Mon, Jul 19, 2010 at 7:26 AM, Phil Blundell <philb@gnu.org> wrote:
> On Mon, 2010-07-19 at 01:24 -0700, Khem Raj wrote:
>> -THUMB_INTERWORK = "yes"
>> +# armv4 does not have thumb instruction set therefore no interworking instructions
>> +# so if machine is based on armv4 we dont have choice.
>> +
>> +THUMB_INTERWORK_armv4 = "no"
>> +THUMB_INTERWORK ?= "yes"
>
> I don't think this is necessary or desirable. If you are building for
> v4 then the BX instructions ought to be fixed up during final link.
Yes with --fix-v4bx/--fix-v4bx-interworking its possible.
Is
> there a particular problem that you're trying to solve?
>
Not any particular case but some versions of compiler do not pass
flags to --fix-v4bx-interworking ld.
I was thinking its more apt to describe the machine with not
supporting THUMB_INTERWORK
hmmm but I now I see that we will need it for v4/EABI support. So
better fix the compiler.
> p.
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
next prev parent reply other threads:[~2010-07-19 16:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 8:24 [PATCH] sane-toolchain.inc: THUMB_INTERWORK should not be defined for armv4 and add armv4 to ARM EABI supporting architectures Khem Raj
2010-07-19 14:26 ` Phil Blundell
2010-07-19 16:29 ` Khem Raj [this message]
2010-07-19 16:46 ` Phil Blundell
2010-07-19 17:34 ` Khem Raj
2010-07-19 20:20 ` Phil Blundell
2010-07-19 22:42 ` Khem Raj
2010-07-19 22:49 ` Khem Raj
2010-07-20 7:11 ` Phil Blundell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTikuwarIRXUIOX1L2A2LBD7D-Rhglsd-Rur8QaOO@mail.gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox