From: Lewis Zhou <lewisou@gmail.com>
To: Austin Morton <austinpmorton@gmail.com>
Cc: barebox@lists.infradead.org, crossgcc maillist <crossgcc@sourceware.org>
Subject: Re: selected processor does not support `rev r7,r7'
Date: Thu, 21 Mar 2019 16:49:18 +0800 [thread overview]
Message-ID: <CAD_PvuaROBDHod3XjFFgZ6Qic3pHhRSP=qFbQ5MHwGJs=js+0g@mail.gmail.com> (raw)
In-Reply-To: <CAPWKHJSLmc1+-rV0rZeGn37uhkWwKsqmWXZSGJAs32zLE=Hxtg@mail.gmail.com>
Hi Austin,
Here's the list. armv7-a is on the list.
lewis@lewis-ubuntu:~/x-tools/arm-cortex_a8-linux-gnueabihf/bin$
./arm-cortex_a8-linux-gnueabihf-gcc -E -march=help -xc /dev/null
arm-cortex_a8-linux-gnueabihf-gcc: error: unrecognized -march target: help
arm-cortex_a8-linux-gnueabihf-gcc: note: valid arguments are: armv2
armv2a armv3 armv3m armv4 armv4t armv5 armv5t armv5e armv5te armv5tej
armv6 armv6j armv6k armv6z armv6kz armv6zk armv6t2 armv6-m armv6s-m
armv7 armv7-a armv7ve armv7-r armv7-m armv7e-m armv8-a armv8.1-a
armv8.2-a armv8.3-a armv8.4-a armv8-m.base armv8-m.main armv8-r iwmmxt
iwmmxt2
arm-cortex_a8-linux-gnueabihf-gcc: error: missing argument to '-march='
That's strange. When compiling both barebox and linux. I always got errors like:
"selected processor does not support `rev r7,r7'
Kind regards,
Lewis
On Thu, Mar 21, 2019 at 4:40 PM Austin Morton <austinpmorton@gmail.com> wrote:
>
> Any recent version of gcc should spit out a list of supported March values if invoked with an invalid value. (read gcc 7 or higher).
>
> What does this command output on your compiler?
>
> # gcc -E -march=help -xc /dev/null
>
> https://stackoverflow.com/questions/47299458/how-can-i-determine-what-architectures-gcc-supports
>
> On Thu, Mar 21, 2019, 04:25 Lewis Zhou <lewisou@gmail.com> wrote:
>>
>> Hi,
>>
>> I recently tried to compile the barebox bootloaer with the
>> arm-cortex_a8-linux-gnueabihf configuration which is based on the
>> sample configuration arm-cortex_a8-linux-gnueabi with the hardware
>> float enabled.
>>
>> However, the compiler (gcc) seems not support -march=armv7-a flag. I
>> think something is wrong as the cortex_a8 is a sub-architecture of
>> armv7-a.
>>
>> The toolchain failed to compile both the barebox and the linux kernel
>> (4.19). Please help! Attached is a response from the barebox mailing
>> list.
>>
>>
>> Kind regards,
>> Lewis
>>
>> ---------- Forwarded message ---------
>> From: Sascha Hauer <s.hauer@pengutronix.de>
>> Date: Thu, Mar 21, 2019 at 4:06 PM
>> Subject: Re: selected processor does not support `rev r7,r7'
>> To: Lewis Zhou <lewisou@gmail.com>
>> Cc: <barebox@lists.infradead.org>
>>
>>
>> On Thu, Mar 21, 2019 at 03:53:06PM +0800, Lewis Zhou wrote:
>> > Hi Sascha,
>> >
>> > Here's the log:
>> >
>> > make -f scripts/Makefile.build obj=common
>> >
>> > arm-cortex_a8-linux-gnueabihf-gcc -Wp,-MD,common/.memory.o.d
>> > -nostdinc -isystem
>> > /home/lewis/x-tools/arm-cortex_a8-linux-gnueabihf/lib/gcc/arm-cortex_a8-linux-gnueabihf/8.3.0/include
>> > -D__KERNEL__ -D__BAREBOX__ -Iinclude
>> > -I/home/lewis/OpenProj/barebox/dts/include
>> > -I/home/lewis/OpenProj/barebox/arch/arm/include
>> > -I/home/lewis/OpenProj/barebox/arch/arm/include -include
>> > /home/lewis/OpenProj/barebox/include/linux/kconfig.h -fno-builtin
>> > -ffreestanding -D__ARM__ -fno-strict-aliasing -marm -mlittle-endian
>> > -mabi=aapcs-linux -mno-thumb-interwork -D__LINUX_ARM_ARCH__=7
>> > -march=armv5t -Wa,-march=armv7-a -msoft-float -mthumb
>>
>> -march=armv5t -Wa,-march=armv7-a shouldn't be here. It comes from this
>> line in arch/arm/Makefile:
>>
>> arch-$(CONFIG_CPU_32v7) :=-D__LINUX_ARM_ARCH__=7 $(call
>> cc-option,-march=armv7-a,-march=armv5t -Wa$(comma)-march=armv7-a)
>>
>> This means the build process will use "-march=armv7-a" when the compiler
>> supports it. Apparently it does not, so it will fall back to
>> "-march=armv5t -Wa,-march=armv7-a". armv5t doesn't support thumb2 code,
>> only thumb and as it seems thumb does not support the "rev" instruction.
>>
>> Your compiler should really support "-march=armv7-a". If it doesn't I
>> really think there is something wrong with it.
>>
>> Sascha
>>
>> --
>> Pengutronix e.K. | |
>> Industrial Linux Solutions | http://www.pengutronix.de/ |
>> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
>> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2019-03-21 8:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 4:57 Lewis Zhou
2019-03-20 7:52 ` Sascha Hauer
2019-03-21 1:03 ` Lewis Zhou
2019-03-21 7:33 ` Sascha Hauer
2019-03-21 7:53 ` Lewis Zhou
2019-03-21 8:06 ` Sascha Hauer
[not found] ` <CAD_PvuY8oVy3Ny65bcF2a3LPC0R4+8uXCu6qda6CcbY+Ji+3JQ@mail.gmail.com>
[not found] ` <CAPWKHJSLmc1+-rV0rZeGn37uhkWwKsqmWXZSGJAs32zLE=Hxtg@mail.gmail.com>
2019-03-21 8:49 ` Lewis Zhou [this message]
2019-03-21 9:25 ` Juergen Borleis
2019-03-22 1:02 ` Lewis Zhou
2019-03-22 8:07 ` STM32MP1 SoC support in latest Barebox gianluca
2019-03-22 9:31 ` gianluca
2019-12-25 8:32 ` Ahmad Fatoum
2019-03-22 9:46 ` Yann Sionneau
2019-03-22 11:24 ` Robert Schwebel
2019-03-22 1:22 ` selected processor does not support `rev r7,r7' Lewis Zhou
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='CAD_PvuaROBDHod3XjFFgZ6Qic3pHhRSP=qFbQ5MHwGJs=js+0g@mail.gmail.com' \
--to=lewisou@gmail.com \
--cc=austinpmorton@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=crossgcc@sourceware.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