Folks, In preparation for adding aarch64 string functions into
cortex-strings, I'd like feed back on the following series of patches.
1/5 Trivial whitespace cleanups.
2/5 Autotools foo for cross building support.
3/5 Autotools foo for architecture detection.
4/5 Missing LDADD and CFLAGS setting.
5/5 Use --std=gnu99
I'm particularly interested in views on 3/5. This patch sets
direction for autoconf detection of the host architecture. The
intention is that we retain the single toplevel Makefile.am which
gains AM_CONDITIONAL support for the detected host triple.
The aarch64 specific code will follow in a different patch set.
Cheers
/Marcus
Hi,
the issue seems indeed to be introduced by r193959 and fixed in
r194161, as it is reported in:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55571
Unfortunately, my merge attempt was at r190461 :(
I redo the merge...
Yvan
Summary:
* Validate RM toolchain, Linaro QENU 2012.12 and Linaro aarch64 2012.11.
* Collect performance data for different branch cost.
Details:
* Validate RM toolchain release.
* Set up test environment with the help of Michael and validate Linaro
QEMU 2012.12 release.
* Validate aarch64 toolchain 2012.11. From 2012.12, it will be
released regularly like arm-linux-gnueabihf toolchain.
* Collect denbench and spec2000int performance data for branch cost tuning.
* Investigate how to do copy propagation for shrink-wrap to optimize
453.povray benchmark. Will reuse current codes in pass_cprop_hardreg.
Plans:
* Performance reports for branch cost tuning.
* Fix README issue (lp:1068402) in Linaro crosstool-ng.
Best regards!
-Zhenqiang
Hi all，
I am a rookie, and now I'm focusing on ARM virtualization. As we know,KVM (for Kernel-based Virtual Machine) is a full virtualization solution. KVM-Autotest is a set of virtualization tests for X86 platform, but it may not be suitable for ARM.I want to know, in the linaro , what tools can protect the KVM and qemu quality ? Thanks and Regards,Qun Chen
* usual set of meetings etc
* rebased qemu-linaro on upstream 1.3, rolled tarball for 2012.12;
Zhenqiang has tested it and it should be ready to go next week
* qemu arm patch catchup; pinging or resending some patches of
mine from before upstream freeze
* applied a set of boot-wrapper patches from tixy
* virtio patch code review: design definitely coming together now
KVM blueprint progress tracker (note new url):
http://cbuild.validation.linaro.org/helpers/backlog?group_by=topic&colour_b…
-- PMM
== Progress ==
* Turn off 64-bits bitos in Neon: Ping-ed patch proposal.
* Disable peeling: benchmarks show good results; sent a proposal
upstream to discuss preliminary implementation & needed testsuite
modifications.
* builtin_bswap16 backport to linaro-4.7: need to investigation an
unexpected regression reported for i686 target.
* Updated gdb linaro sources to 7.5.1, exercising the release process.
* Trying to bootstrap gcc-linaro/4.7 on board: need to retry with a
different rootfs distribution.
== Next ==
* handle 64-bits bitops in Neon and disable-peeling feedback from
upstream if any.
* finish builtin_bswap16 backport
== Blueprints ==
Initial Current Actual
initial-aarch64-backport 31 Oct 2012 14 Dec 2012
aarch64-baremetal-testing 31 Oct 2012 14 Dec 2012
fix-gcc-multiarch-testing 31 Dec 2012 31 Dec 2012
backport-fma-intrinsic 31 Dec 2012 31 Dec 2012
fused-multiply-add-support 31 Dec 2012 31 Dec 2012
gcc-investigate-lra-for-arm 31 Dec 2012 31 Dec 2012
== Progress ==
* Admin
* Interviewing
* Took over from Michael
* Preparation for taking over from Michael
* re-PINGed triplet backport patches upstream
* Patch review
* Initial thoughts about cards
== Next Week ==
* initial-aarch64-backport and aarch64-baremetal-testing
* Complete documentation
* gcc-investigate-lra-for-arm
* Analyse benchmarks
* Run HOT/COLD partitioning benchmarks
* Analyse ARM results
* On x86_64 to see what the actual benefit we could get
* fix-gcc-multiarch-testing
* Come up with strawman proposal for updating testsuite to handle
testing with varying command-line options.
== Future ==
* backport-fma-intrinsic & fused-multiply-add-support
* Backport patches once fix-gcc-multiarch-testing has been done.
--
Matthew Gretton-Dann
Linaro Toolchain Working Group
matthew.gretton-dann(a)linaro.org
Hi,
I am trying to compile UEFI code with linaro toolchain version:
# arm-linux-gnueabi-gcc --version
arm-linux-gnueabi-gcc (Ubuntu/Linaro 4.7.1-5ubuntu1~ppa1) 4.7.1
Copyright (C) 2012 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
I got the erros as follows:
"/usr/bin/arm-linux-gnueabi-gcc" -mthumb -march=armv7-a
-I/home/shiva/workspace/arndale/edk2/SamsungPlatformPkg/ExynosPkg/Exynos5250/Include/Platform
-g -Os -fshort-wchar -fno-strict-aliasing -Wall -Werror -Wno-missing-braces
-Wno-array-bounds -c -include AutoGen.h -mword-relocations -mlittle-endian
-mabi=aapcs -mapcs -fno-short-enums -save-temps -fsigned-char
-ffunction-sections -fdata-sections -fomit-frame-pointer -Wno-address -O0
-o
/home/shiva/workspace/arndale/edk2/Build/Arndale-Exynos/DEBUG_ARMLINUXGCC/ARM/SamsungPlatformPkg/ExynosPkg/Exynos5250/Sec/Sec/OUTPUT/./Smc.obj
-I/home/shiva/workspace/arndale/edk2/SamsungPlatformPkg/ExynosPkg/Exynos5250/Sec
-I/home/shiva/workspace/arndale/edk2/Build/Arndale-Exynos/DEBUG_ARMLINUXGCC/ARM/SamsungPlatformPkg/ExynosPkg/Exynos5250/Sec/Sec/DEBUG
-I/home/shiva/workspace/arndale/edk2/MdePkg
-I/home/shiva/workspace/arndale/edk2/MdePkg/Include
-I/home/shiva/workspace/arndale/edk2/MdePkg/Include/Arm
-I/home/shiva/workspace/arndale/edk2/MdeModulePkg
-I/home/shiva/workspace/arndale/edk2/MdeModulePkg/Include
-I/home/shiva/workspace/arndale/edk2/ArmPkg
-I/home/shiva/workspace/arndale/edk2/ArmPkg/Include
-I/home/shiva/workspace/arndale/edk2/ArmPlatformPkg
-I/home/shiva/workspace/arndale/edk2/ArmPlatformPkg/Include
-I/home/shiva/workspace/arndale/edk2/SamsungPlatformPkg/ExynosPkg/Exynos5250
-I/home/shiva/workspace/arndale/edk2/SamsungPlatformPkg/ExynosPkg/Exynos5250/Include
/home/shiva/workspace/arndale/edk2/SamsungPlatformPkg/ExynosPkg/Exynos5250/Sec/Smc.c
Smc.s: Assembler messages:
Smc.s:51: Error: selected processor does not support Thumb mode `smc 0'
Is there any issue with the toolchain or any flags I am using?
--
Thanks and Regards,
Shiva.
