From: jamie@shareable.org (Jamie Lokier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Always generate the IT instruction when compilingfor Thumb-2
Date: Thu, 28 Jan 2010 14:55:30 +0000 [thread overview]
Message-ID: <20100128145530.GC24679@shareable.org> (raw)
In-Reply-To: <1264683904.7064.57.camel@pc1117.cambridge.arm.com>
Catalin Marinas wrote:
> On Wed, 2010-01-27 at 22:02 +0000, Russell King - ARM Linux wrote:
> > On Tue, Jan 26, 2010 at 10:14:24AM +0000, Catalin Marinas wrote:
> > > Current behaviour is to generate the IT instruction only for Thumb-2
> > > code. However, the kernel helpers in entry-armv.S are compiled to ARM in
> > > a unified syntax file (if THUMB2_KERNEL). Recent compilers warn about
> > > missing IT instruction in unified assembly syntax files. The patch
> > > changes the "-mimplicit-it" gas option to "always".
> >
> > Any downsides to this change? Any assemblers not accepting "always"
> > instead of "thumb" ?
>
> When the -mimplicit-it was merged into mainline gas, it supported all of
> thumb, arm, always and never. We still have the old -mauto-it but that's
> I think only valid for the CodeSourcery toolchains.
I notice there's a few "it" dotted around the kernel code now. In
fact, that's how I learned about it - because I thought "that can't be
right when targetting ARM", and did some reading to learn otherwise.
With -mimplicit-it=always, they should not be needed. So they can be
removed from the kernel source?
Or, if it's policy to put "it" in all the places needed, wouldn't
-mimplicit-it=arm (the gas default) be a better choice, to make sure
they are in all the places needed?
-- Jamie
next prev parent reply other threads:[~2010-01-28 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 10:14 [PATCH] ARM: Always generate the IT instruction when compiling for Thumb-2 Catalin Marinas
2010-01-27 22:02 ` Russell King - ARM Linux
2010-01-28 13:05 ` [PATCH] ARM: Always generate the IT instruction when compilingfor Thumb-2 Catalin Marinas
2010-01-28 14:55 ` Jamie Lokier [this message]
2010-01-28 15:50 ` Catalin Marinas
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=20100128145530.GC24679@shareable.org \
--to=jamie@shareable.org \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.