From: Dave.Martin@arm.com (Dave Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: __ARM_ARCH_2__
Date: Thu, 8 Aug 2013 19:23:00 +0100 [thread overview]
Message-ID: <20130808182300.GD2356@localhost.localdomain> (raw)
In-Reply-To: <1375985035.647275432@f399.i.mail.ru>
On Thu, Aug 08, 2013 at 10:03:55PM +0400, Alexander Shiyan wrote:
> > On Thu, Aug 08, 2013 at 09:27:19AM +0100, Russell King - ARM Linux wrote:
> > > On Thu, Aug 08, 2013 at 10:08:02AM +0800, zhaobin xv wrote:
> > > > I don't know what the"__ARM_ARCH_2__" mean?
> > > > "__ARM_ARCH_2__" is definded by gcc or definded byarmlinux?
> > > > where does it come from? what does it want to do?
> > >
> > > You could try a few things before posting:
> > >
> > > 1. You could try grepping the kernel source to find out if anything
> > > in the kernel defines it.
> > > 2. You could try asking google and seeing what it returns.
> > >
> > > Either of those will tell you that it's not defined by the kernel but by
> > > the compiler. For me, the first link on google explains it really well.
> >
> > Should that code go away? I believe we don't support v2 or v3 any more...
> > Did teqp actually work in 32-bit modes?
>
> "ARM: 7770/1: remove residual ARMv2 support from decompressor":
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/arch/arm/boot/compressed/head.S?id=52c08a9e399739979027ea1e463f5529476da104
Job done, then
Cheers
---Dave
prev parent reply other threads:[~2013-08-08 18:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 2:08 __ARM_ARCH_2__ zhaobin xv
2013-08-08 8:27 ` __ARM_ARCH_2__ Russell King - ARM Linux
2013-08-08 17:52 ` __ARM_ARCH_2__ Dave Martin
2013-08-08 18:03 ` __ARM_ARCH_2__ Alexander Shiyan
2013-08-08 18:23 ` Dave Martin [this message]
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=20130808182300.GD2356@localhost.localdomain \
--to=dave.martin@arm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).