Please configure eglibc with
rtlddir=/lib
libdir=/usr/lib/arm-linux-gnueabihf
slibdir=/lib/arm-linux-gnueabihf
or
rtlddir=/lib
libdir=/usr/lib/arm-linux-gnueabi
slibdir=/lib/arm-linux-gnueabi
Thanks!
-Zhenqiang
From: linaro-toolchain-boun...@lists.linaro.org
[mailto:linaro-toolchain-boun...@li
== Issues ==
* None.
== Progress ==
* Update "Keep constants in register when expanding" patch according
to comments (TCWG-486, 3/10).
* Refine ccmp patches since the old ones can not apply (TCWG-488, 2/10).
* Check PR62151, it was exposed by my commit r211885. But the root
cause was r208165.
*
== Issue ==
* None.
== Progress ==
* Refine and send the patch to fix pr61225 in Combine pass for review (2/10).
* Send out the ARM backend patch to keep some constant in register
(TCWG-486, 2/10).
* Rebase and test ccmp related patches (TCWG-488, 2/10).
* R/M toolchain related work (4/10).
==
== Issues ==
* None.
== Progress ==
* Rework the patch to fix pr61225 in Combine pass. (4/10)
* Investigate code-size regression when skipping arm_split_constant in
expand (TCWG-486, 4/10).
- For reg & 0x, zero_extendhi instruction is more efficient.
- For "PLUS", the define_insn_and_sp
On 1 August 2014 03:36, Joel (Xi Zhou) Zhou wrote:
> Hi guy,
>
> In order to have soft-float support in toolchain, I tried to build our
> toolchain using Linaro ct-ng script.
> I used "linaro-armeb-linux-gnueabihf" configuration then change floating
> point option from hard to soft.
>
> There is
== Progress ==
* One day off.
* Test and send out the local NLS patch for community review (1/10).
* Test ccmp patches. Can not reproduce a FAIL in previous regression
test with the latest trunk(TCWG-488, 1/10).
* Test codes to skip arm_split_constant (TCWG-486, 3/10). Performance
results seam OK
== Issue ==
* None.
== Progress ==
* Enable binutils plugins for Linaro crosstool-ng samples (lp: 1335316).
* Update ccmp patches (TCWG-488, 5/10)
- Update two ccmp patches according to comments
- Enhance the patch to handle cmov instructions.
* Constant optimization (TCWG-486, 2/10): Logs s
== Issues ==
* None
== Progress ==
* Take care Linaro binaries release (1/10).
* Send out ccmp patches for community review (TCWG-488, 1/10).
* loop2_invariants heuristics tune (1/10, TCWG-469). One patch was
committed @r212135.
* Constant optimization (TCWG-486, 7/10 )
- Try to keep constant
On 23 June 2014 21:44, wrote:
> Hello,
>
> I am trying to crosscompile on my laptop for an arm v7 processor, using the
> linaro toolchain.
>
> I downloaded the following :
>
>
> http://releases.linaro.org/14.05/components/toolchain/binaries/gcc-linaro-arm-linux-gnueabihf-4.9-2014.05_linux.tar.xz
== Issues ==
* None.
== Progress ==
* loop2-invariant heuristics tuning (TCWG-469, 2/10). Two patches were
committed @r211818 and r211885. Another two are in review.
* Test the rebased ccmp patches (TCWG-488, 2/10).
* Send out a patch to enhance cprop pass by checking rtx_cost. Collect
benchmark
The latest binaries release is at
http://releases.linaro.org/latest/components/toolchain/binaries
unzip one tarball, you can find the README and all pdf documents.
On 18 June 2014 23:13, Christophe Lyon wrote:
> 4.5 is now very old. I suspect you actually downloaded the source version.
>
> I thi
you have an example benefited from your
cse changes? I want to verify it on ARM.
Thanks!
-Zhenqiang
> Thanks,
> Andrew Pinski
>
> -Original Message-
> From: linaro-toolchain-boun...@lists.linaro.org
> [mailto:linaro-toolchain-boun...@lists.linaro.org] On Behalf Of
== Issues ==
* None.
== Progress ==
* Work out 4 patches to enhance loop2-invariant heuristics and send
out for community review (TCWG-469, 3/10).
* Test the rebased ccmp patches (TCWG-488, 2/10).
* Investigate how to optimize large constant. Patch is in testing
(TCWG-486, 5/10). Basic idea is:
== Issues ==
* None.
== Progress ==
* One day off.
* Clean up and test loop2-invariant heuristic tune patches (TCWG-469, 6/10).
* Rebase conditional compare patches and split them into smaller ones
(TCWG-488, 2/10).
== Plans ==
* Send out loop2-invariant heuristic tuning patches for review.
*
== Issue ==
* None.
== Progress ==
* Commit the fixes for pr61220, 61278 and part of 61225. The patch to
fix other part of 61225 is still in review (2/10).
* Loop invariant heuristics tuning. Tests are ongoing. (7/10, TCWG-763)
* Rebase conditional compare patches. Tests are ongoing.
* Prepare U
On 27 May 2014 11:59, Denys Dmytriyenko wrote:
> On Tue, May 27, 2014 at 11:17:47AM +0800, Zhenqiang Chen wrote:
>> On 27 May 2014 10:17, Denys Dmytriyenko wrote:
>> > Hi,
>> >
>> > I've been having this issue with latest binary Linaro 2014.04 toolchain
On 27 May 2014 10:17, Denys Dmytriyenko wrote:
> Hi,
>
> I've been having this issue with latest binary Linaro 2014.04 toolchain from
> http://releases.linaro.org/14.04/components/toolchain/binaries/gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux.tar.xz
>
> It comes with own sysroot, but linker f
== Issue ==
* None.
== Progress ==
* Investigate PR61220, 61225 and 61278, which are triggered by my
previous commits. Patches are in review. (9/10)
* Investigate codes generated by shrink-wrapping interrupt routes. It
seams no dwarf info issue.
* Misc update for Linaro crosstool-ng to make the
== Issue ==
* None.
== Progress ==
* Commit three patches to enhance shrink-wrap for loop. But community
reports an ICE in dwarf info with the patches. (TCWG-133, 5/10)
* Update/test shrink-wrap for apcs patch according to comments (TCWG-482, 2/10)
* Loop-invariant heuristic tuning (TCWG-763, 2
== Issue ==
* None.
== Progress ==
* Identify a build environment issue for linux64 gdb binaries "Symbol
format `elf32-littlearm' unknown".
* Send out shrink-wrap related patches from community review (TCWG-133, 2/10)
* Move-loop-invariant heuristic tuning (TCWG-469, 8/10).
- Update heuristic
== Issues ==
* None
== Progress ==
* May 1-2: Laybor day holiday
* Commit fcsel support patch for aarch64 @r209889.
* Tuning move-loop-invariants heuristics for -fira-loop-pressure:
- Record register pressure for each invariant other than a max for all.
- Take register pressure into account
Three ways to fix it:
* Disable multilib.
* apt-get install gcc-multilib g++-multilib
* config gcc with --with-system-zlib
On 4 May 2014 00:48, Reinier Millo Sánchez wrote:
>> Hello,
>> I have a problem building gcc-linaro-arm-linux-gnueabihf
>> toolchain for my x86_64 system. I downlo
== Issue ==
* None
== Progress ==
* More tests on shrink-wrap changes (TCWG-133, 6/10).
- Cortex-m3 tests exposes a data flow issue: New BB created after
dfinit does not have correct df_lr info.
- Collect Spec2k benchmarks on X86-64 and ARM.
* Linaro 4.9 binaries release (2/10).
- Update L
== Issue ==
* None.
== Progress ==
* multilib can not work with multiarch anymore, so change Linaro
crosstool-ng to make 2014.04 release (2/10).
- For 4.8 release, we will revert the change and keep it align with
previous releases.
* Linaro 4.9 toolchain binaries pre-releases (Cross & native)
On 16 April 2014 00:31, Jeremy Hahn wrote:
> Getting the following cross compiling for RPi on Debian Wheezy x64 using
> the gcc-linaro-arm-linux-gnueabihf-raspbian toolchain within Eclipse
> Kepler. Compilation works fine using native Debian x64 GCC and native
> GCC compiler on the RPi.
>
> out of
== Issue ==
* None
== Progress ==
* 2 day off.
* Investigate lp:1304267 and close it as invalid.
* Investigate shrink-wrap bootstrap issues [4/10, TCWG-133]
- Re-implement the copy propagate part by referring cprop_hardreg pass.
- Other tests are ongoing.
* Document cross-native build on wi
u the status
>> soon.
>> Thank you so much for you support. Let me try first.
>>
>>
>> On Fri, Apr 11, 2014 at 6:41 AM, Zhenqiang Chen
>> wrote:
>>>
>>> It seams to me you want a "cross-native" build. The process is similar
>>>
It seams to me you want a "cross-native" build. The process is similar
with "canadian" build. If you want to try linaro crosstool-ng, I will
give you some instructions.
-Zhenqiang
On 11 April 2014 01:41, Anwej Alam wrote:
> Dear Sir,
>
> Thank you so much for your reply.
>
> I would like to tell
== Issue ==
* None
== Progress ==
* Half day sick leave.
* Create a 64-bit raspbian toolchain for customer.
* Recreate roots tarballs needed for cbuildv1 cross validation.
* Backport r208511 to linaro 4.8 to fix lp:1273511 and lp:1268893 in
2014.04 release.
* Enhancing shrink-wrap. Get unexpecte
== Issues ==
* None
== Progress ==
* Create prebuilt sysroot based on Linaro eglibc 2014.04 release
(https://launchpad.net/linaro-toolchain-binaries/support/01/+download/linaro-prebuilt-sysroot-2014.04.tar.bz2)
(1/10).
* Enable shrink-wrap for apcs. Patch was out for community review. (1/10)
*
== Issues ==
* None
== Progress ==
* Identify a missing instruction pattern which blocks fcsel
optimization. A patch was sent out for community review. [2/10,
TCWG-309]
* Identify a ICE when handling dwarf-info in ARM backend when testing
shrink-wrap. A fix was committed to trunk. [2/10]
* Reb
== Issues ==
* None
== Progress ==
* Validate R/M toolchain 4.8 q1 update release.
* Try Cross-Native build based on Linaro crosstool-ng.
* Handle conditional compare in ifcvt.c to make ccmp and csel work together.
* Read document about FCMP/FCCMP and investigate on how to generate
FCCMP instr
On 13 March 2014 07:42, Felipe Rocha da Rosa wrote:
>
>> On 12 March 2014 09:57, Renato Golin wrote:
>> > On 11 March 2014 23:47, Felipe Rocha da Rosa
>> > wrote:
>> >> I'm trying to build the native compiler to a arm a9 using this
>> >> tutorial,
>> >> https://wiki.linaro.org/WorkingGroups/Tool
___
>> From: linaro-toolchain-boun...@lists.linaro.org
>> on behalf of Diane Holt
>>
>> Sent: Wednesday, March 05, 2014 2:33 PM
>> To: Zhenqiang Chen
>> Cc: Linaro Toolchain
>> Subject: Re: Building 4.8 without multilib
>
needs to be prepared
>> for multi-lib headers before you do a multi-lib enabled gcc build.
>>
>> So, what I did was identify the multi-lib configurations that are
>> enabled when I selected a particular --target.
>>
>> Take that information and build the kernel hea
needs to be prepared
>> for multi-lib headers before you do a multi-lib enabled gcc build.
>>
>> So, what I did was identify the multi-lib configurations that are
>> enabled when I selected a particular --target.
>>
>> Take that information and build the kernel hea
== Issues ==
* None
== Progress ==
* CCMP for AARCH64.
- Design cases to cover most conditional compare combinations.
- Set up qemu environment and run regression tests. And fix all the new FAILs.
* Respawn 2014.01-01 baremental toolchains by setting
CT_TARGET_LDFLAGS=" --specs=rdimon.specs
== Issues ==
* None
== Progress ==
* Take care lp: 1270040, lp:1278337 and Beagleboard "Abort" issue.
* Respawn 2014.01 release to use newlib-linaro-2.1.0-2014.02 for
baremetal toolchains
(http://cbuild.validation.linaro.org/binaries/2014.01-01/)
* Test codes to duplicate shared compares to get
Can you try to replace pthread and libstdc++ related libraries on your
beagleboard with the ones released in Linaro toolchain?
Thanks!
-Zhenqiang
On 18 January 2014 02:49, Koen Kooi wrote:
> This should match what we have in meta-linaro/dora, which is the linaro
> 2013.12 toolchain release.
>
>
== Issues ==
* None
== Progress ==
* Jan. 31 - Feb. 6: Chinese Spring Festival holidays .
* Test codes to duplicate shared compares to get more conditional
compares. But still get unexpected bootstrap fail on Chrome book.
* Test codes to enable shrink-wrap for TARGET_APCS_FRAME.
* Update patch
On 8 February 2014 07:37, Evan Carson wrote:
> Hello,
>
> I'm maintaining an older release we have which uses the older toolchian
> binaries in gcc-linaro-arm-linux-gnueabi-2012.03-20120326_linux. I've
> identified a bug in glibc we appear to be encountering and would like to
> port the fix back.
== Issues ==
* None
== Progress ==
* Investigate to duplicate shared compares to get more conditional compares.
* Investigate to enable shrink-wrap for TARGET_APCS_FRAME. Still some
ICE fails in regression tests.
* Help on cbuilv2 eglibc multilib build issues.
== Plans ==
* Tuning ccmp perfor
== Issues ==
* None.
== Progress ==
* Test Linaro cbuildv2.
- Write a reference script to support windows installer in cbuildv2.
- Do some basic validation work against the binaries built from cbuildv2.
* Reproduce and work out a patch for "ICE when building
linux-linaro-tracking" (lp:126889
Trunk also has ICE. Root cause: dwarf info is partly updated in
arm_emit_vfp_multi_reg_pop when enabling shrink-wrap.
I will report a FSF GCC bug and fix it later.
Thanks!
-Zhenqiang
On 14 January 2014 15:43, Zhenqiang Chen wrote:
> Thank you! I can reproduce it with options:
>
> n
://bugs.launchpad.net/gcc-linaro
If this blocks your work, please remove "-g' option to workaround it.
Thanks!
-Zhenqiang
On 14 January 2014 15:09, Koen Kooi wrote:
> On 01/14/2014 02:39 AM, Zhenqiang Chen wrote:
>>
>> I tries Linaro standard build. And I can not reprodu
3 January 2014 09:19, Zhenqiang Chen
>> wrote:
>>>
>>> Can you attach the preprocessed C file? Add option --save-temps to
>>> compile neon4 source file. Then you will get a temp file neon4.i
>>>
>>> Thanks!
>>> -Zhenqiang
>>>
>
Can you attach the preprocessed C file? Add option --save-temps to
compile neon4 source file. Then you will get a temp file neon4.i
Thanks!
-Zhenqiang
On 13 January 2014 14:56, Koen Kooi wrote:
> Hi,
>
> I've been playing with linux-linaro-tracking and the 2013.12 (and 2013.10,
> 2013.11) tool
== Issues ==
* None.
== Progress ==
* Try cbuildv2 and compare the binaries with current releases.
* Identify MULTIARCH_DIRNAME in trunk breaks aarch64 multiarch build.
* Branch-cost tune for Cortex-M.
== Plans ==
* Verify binaries built from cbuildv2
== Planed leaves ==
* Jan. 30 - Feb. 10
== Issues ==
* None
== Progress ==
* One day off (Jan. 1)
* Do some basic validations for 2013.12 toolchain binaries release.
* R/M Mac toolchain validation
* Branch-cost related tuning for Cortex-M.
== Plans ==
* Continue on branch-cost related tuning.
__
== Issues ==
* None
== Progress ==
* One day off (Dec. 27).
* Prepare toolchain binaries release
- Backport the newlib patches for ftruncate() and truncate() stubs
- Test and update binutils version to linaro-2.24-2013.12 and
workaround gold compile fail issue.
* Retest -fira-loop-pressure
Thanks for the info. Just try the patch. It did fix the two test cases
in PR 59303.
-Zhenqiang
On 23 December 2013 09:19, Pinski, Andrew
wrote:
>
>
>> On Dec 22, 2013, at 5:17 PM, "Zhenqiang Chen"
>> wrote:
>>
>> == Issues ==
>>
>> * Non
== Issues ==
* None.
== Progress ==
* Rebase aarch64 build scripts to crosstool-ng upstream, test and send
out the patch for community review (2/10).
* Investigate
https://ci.linaro.org/jenkins/job/openembedded-armv8b-rootfs/gcc_version=4.8,label=build,rootfs=minimal/60/console.
It seams build
orrect?
>>
>>
>>
>> If correct, my gut feeling is it might be a problem related to ARM/Thumb
>> mode switch.
>>
>>
>>
>> BR,
>>
>> Terry
>>
>>
>>
>> From: Parimala Baggiri [mailto:baggiriparim...@gmail.com]
&
On 19 December 2013 13:36, Parimala Baggiri wrote:
> Hello,
>
> I am using the pre-built toolchain gcc-arm-none-eabi-4_6-2012q2 from linaro
> to compile u-boot (u-boot-linaro-stable) and to compile my standalone
> applications to run on target(PandaBoard ES rev b2)
>
> hello_world standalone appli
== Issues ==
* None.
== Progress ==
* Enable libomp for aarch64*-linux-gnu builds in Linaro crosstool-ng.
* Backporting r200103 and r205509 to Linaro 4.8.
* Try to enable lra and test Spec2k with -fno-move-loop-invariants and
-fira-loop-pressure. But still no overall performance improvement.
(2/
== Issues ==
* None.
== Progress ==
* 1.5 days off.
* Misc update for Linaro crosstool-ng
- Re-enable parallel build for do_cc_core.
- Add linaro-armeb-none-eabi config.
- Update all CT_TOOLCHAIN_PKGVERSION to "Linaro GCC 2013.11"
* Share toolchain binaries configures to cbuild2 group.
* B
== Issues ==
* None.
== Progress ==
* Commit the fix for test case (lp1243022.c) by skipping arm-neon.
* Spawn arm-none-eabi build for Linaro 2013.11 release.
* Report PR59282: SPEC2K 252.eon ICE.
* Rebase conditional compare patch to trunk and tests.
- Update simplify_while_replacing to skip
== Issues ==
* None.
== Progress ==
* Commit the patch to support S2 system register
in AARCH64 GAS.
* Identify the issue files in parallel build fail (PR57683) and
backport r197467 and r198999 to FSF GCC 4.8.
* Verify Linaro crosstool-ng to make sure Fortran is supported in all builds.
* Tr
On 22 November 2013 15:58, Victor Chong wrote:
> Hi YongQin,
>
> You can go to TCWG's FAQ page at
> https://wiki.linaro.org/WorkingGroups/ToolChain/FAQ (Q7) to get a detailed
> explanation on the naming conventions and also the difference between gnu
> and elf.
>
> Hi TCWG guys,
>
> Sorry but may
On 21 November 2013 12:06, Trevor Woerner wrote:
> On 20 November 2013 21:57, Zhenqiang Chen wrote:
>>> Does anyone know if gcc-arm-embedded has things the Linaro toolchain
>>> doesn't wrt Cortex M0, M3, and M4 device/instruction support?
>>
>> Yes. The
On 21 November 2013 10:44, Trevor Woerner wrote:
> Hi toolchain gurus,
>
> I am about to start some projects working with CortexMx devices and am
> wondering if anyone has an opinion on which toolchain(s) I should
> use/investigate?
>
> Being a fan of Linaro, my first instinct would be to use cbui
== Issues ==
* None.
== Progress ==
* One day (Nov. 15) off.
* Misc update for Linaro crosstool-ng
- Use newlib-linaro-2.0.0-2013.11-1.
- Update fortran support related scripts and configs according to
Matt's comments.
* Propose to support S2 system register in AARCH64 GAS.
- Yufeng fo
== Issues ==
* Binaries build FAIL in cbuild, but OK in local build.
== Progress ==
* Misc update for Linaro crosstool-ng
- Update newlib to 2013.11.
- Modify scripts to meet the check of A-profile multilib support.
- Add fortran/libfortran support for bare metal build.
- Fix multi-lib c
== Issues ==
* None
== Progress ==
* Commit the fix for lp:1243022 on trunk.
* Backporting r203603, r204247 and r203267 to Linaro gcc 4.8.
* Updating CCMP patch according to comments.
* Collect spec2K result for CCMP.
- Overall there is no regression and no improvement.
- 175.vpr is sensiti
== Issue ==
* Can not attend LCU'13 due to slow US Visa process.
== Progress ==
* Investigate lp:1243022:
- Root cause: REG_INC note is lost in subreg2 pass, so ira gets
wrong result in function validate_equiv_mem.
- Work out a patch for community review.
* Send conditional compare (CCMP) pa
On 23 October 2013 10:03, Chris Ruehl wrote:
>
> On Wednesday, October 23, 2013 09:45 AM, Zhenqiang Chen wrote:
>>
>> On 23 October 2013 09:33, Chris Ruehl wrote:
>>>
>>> Hi,
>>>
>>> may you think I'm on the wrong list, no not :-)
>&
On 23 October 2013 09:33, Chris Ruehl wrote:
> Hi,
>
> may you think I'm on the wrong list, no not :-)
>
> I currently build my u-boot loader using the linaro tool chain 2013.09
> and run into a problem with the support for JFFS2 where the linker report
> VFP usage where u-boot using softfp for bu
== Issues ==
* None
== Progress ==
* Prepare Linaro toolchain binaries 2013.10 release
- Update EGLIBC version to 2013.10 and enable-profile for AARCH64.
- Generate Linaro prebuilt sysroot for arm-linux-gnueabihf.
* Commit patch to Reassociate X == CST1 || X == CST2 if popcount (CST2
- CST1)
== Issues ==
* Develop machine was broken. Have to resetup the system.
== Progress ==
* Commit fix for pr58423
* Enhance Linaro crosstool-ng
- Fix lp:1232678
- Get EGLIBC version from config files automatically.
- Build aarch64 sysroot to support profile
(https://launchpad.net/linaro-toolc
eabihf/libgcc'
> [ERROR]make[1]: *** [all-target-libgcc] Error 2
> [ALL ]make[1]: Leaving directory
> `/work/software/cortexa9-linaro-build/.build/arm-linux-gnueabihf/build/build-cc-core-shared'
>
> any idea?
> Regards
> ____
> banma
Please try to disable multilib.
On 10 October 2013 11:34, Rick wrote:
> Hi Term,
>
> I have try to us "crosstool-ng-linaro-1.13.1-4.8 "to build myself cross tool
> chain,
> but some problem happened,just before I have used crosstool-ng offcial
> version,
> every thing is fine,I have got my toolc
== Issues ==
* None
== Progress ==
* Update Conditional compare (CCMP) patch according to community comments.
* Investigate how to generate CCMP to support more than two compares.
- Investigate ifcombine to create more CCMP opportunities.
- Enhancing phiopt to handle CCMP case like:
if
== Issues ==
* None
== Progress ==
* 2 day off on Chinese Mid-Autumn Festival
* Update conditional compare (CCMP) patch according to community comments.
* Work out a patch to fix PR 58423.
* Prepare LCU'13 Visa and hotel.
== Plan ==
* Continue on CCMP.
== Panned leaves ==
* Sept. 24 AM: US V
== Issues ==
* None
== Progress ==
* Prepare Linaro toolchain binary 2013.09 release
- Create linaro-prebuilt-sysroot-2013.09.
- Update local patches and all Linaro samples to use
eglibc-linaro-2.18-2013.09.
* Update Conditional compare (CCMP) according to community comments.
Current method
On 12 September 2013 06:00, Michael Hudson-Doyle
wrote:
> Hi,
>
> Thanks to the advice from this list I've managed to build GCC targeting
> aarch64 (thanks!).
>
> Is there some way I can now run the tests in a Foundation model? I
> don't really know how this would work -- I guess using
> aarch64-
== Issues ==
* None
== Progress ==
* Conditional compare (CCMP)
- Design tens of test cases to verify the codes.
- Handle CCMP in vrp pass. If the compare in CCMP can be simplified,
CCMP will be converted to a copy, compare or a bit operator.
- Investigating to handle CCMP in jump-thread r
== Issues ==
* None
== Progress ==
* 2 day off.
* Conditional compare
- Send out RFC and basic support patches for community review.
- Update and design test cases.
- Investigating bootstrap issue when expanding conditional compare
to optimized RTL.
== Plan ==
* Continue on conditio
== Issues ==
* None
== Progress ==
* Investigate and close lp:1208945 and lp:1210713.
- For lp:1208945, libc.so.6 should be at /lib/arm-linux-gnueabihf.
- For lp:1210713, aufs is not a part of standard linux kernel release.
But aufs is supported by Ubuntu release. So maybe need it for future
== Issues ==
* No idea to fix eglibc backtrace issue.
== Progress ==
* Commit (FSF 4.8 and trunk) the fix for lp: 1189445/1208676.
* Enhance Linaro crosstool-ng:
- Fix gcc respin version issue in README.
- Update big-endian multiarch triplet name.
* Investigate eglibc backtrace issue:
- Te
== Issues ==
* None
== Progress ==
* Validate and release Linaro toolchain binaries 2013.07.
* Commit the fix for pr57637.
* Revise patch and test case for lp1189445.
* Separate conditional compare changes to small patches and test.
* Send out the patch of "Reassociate X == CST1 || X == CST2 if
The Linaro Toolchain and Platform Working Groups are pleased to
announce the 2013.07 release of the Linaro Toolchain Binaries, a
pre-built version of Linaro GCC and Linaro GDB that runs on generic
Linux or Windows and targets the glibc Linaro Evaluation Build.
Uses include:
* Cross compiling ARM
== Issues ==
* None
== Progress ==
* Prepare Linaro toolchain binary 2013.07 release.
* Follow-up patches for pr57637.
* Test conditional compare changes based on trunk.
== Plan ==
* Release Linaro toolchain binary 2013.07.
* Send out the conditional compare changes for Linaro internal revie
On 23 July 2013 14:30, wrote:
> Hi,
>
> I am new to the linaro toolchain and have two questions don't find an
> explicit answer. Help you experts can help.
>
> 1. Can I use linaro arm toolchain to build application for armv5t core?
> My box is a arm926ejs.
Linaro toolchain binary is configured f
== Issues ==
* None
== Progress ==
* Enable multi-arch for Linaro aarch64-linux-gnu build.
- Configure gcc with --enable-multiarch.
- Backport eglibc patches for rtlddir.
- Configure eglibc to set libdir, slibdir and rtlddir.
* Follow up the patch for pr57637.
* Reassociate X == CST1 || X
On 17 July 2013 23:16, Siarhei Siamashka wrote:
> On Wed, 17 Jul 2013 16:52:49 +0200
> Christophe Lyon wrote:
>
>> Hi,
>>
>> Linaro is NOT an alternative to the Yocto project; we are
>> collaborating with them. For instance, there are recipes to build a
>> Yocto distribution using Linaro packages
On 6 July 2013 03:24, 常桓 wrote:
> Hi Linaro toolchain team,
>
> I compiled linaro-toolchain 2013.06 by myself on fedora 18 x86_64,
> everything works fine except GDB.
How do you build the toolchain?
If you use Linaro build scripts (crosstool-ng-linaro) and follow the
README, you should have the
== Issues ==
* None
== Progress ==
* Investigate library dir issue in aarch64-linux-gnu release.
- Crosstool-ng should not link lib64 to lib.
- Eglibc used in Linaro release is too old. No configure to change
lib to lib64.
- Runtime tarball should not assume multiarch (aarch64 gcc does not
== Issues ==
* None
== Progress ==
* Investigate big endian toolchain build in Linaro crosstool-ng.
- Fix an aarch64 triple name issue.
- Add Linaro armeb-linux-gnueabihf, aarch64_be-linux-gnu and
aarch64_be-none-elf configs for big endian builds.
- Please find the reference builds at:
http
== Issues ==
* None
== Progress ==
* Investigate conditional compare RTL representation.
- Fix new fails when expanding conditional compare to cmp_and/cmp_ior.
* Identify the root cause for pr57637.
== Plan ==
* Continue on conditional compare.
_
== Issues ==
* None
== Progress ==
* Investigate conditional compare RTL representation.
- Expand conditional compare to cmp_and/cmp_ior.
- Test is ongoing
* Investigate lp: 1189445. Patch is in testing.
* Identify the root cause for lp: 1189448. FSF4.8 does not have the
buggy code. Linaro
== Issues ==
* None
== Progress ==
* Test and send out shrink wrapping improvement patch for review (TCWG-133).
* Update aarch64-none-elf TARGET_CFLAGS to " -g -O2 ".
* Enable aarch64 gdb build for Windows (lp:1187862).
* Investigate conditional compare RTL representation.
- Trying to expan
== Issues ==
* None
== Progress ==
* Shrink wrapping improvement (TCWG-133)
- Call copyprop to optimized the parameter register move instructions.
- Test is ongoing.
* Update aarch64-none-elf toolchain newlib version to 2.0~20130530 (lp:1185711).
== Plan ==
* Collect performance data for
On 29 May 2013 18:24, BHARATH H S wrote:
> Hi,
> I have a usecase where linaro toolchain is used to build my executables and
> the sysroot is copied and used as glibc for running my embedded system.
> Reason for this is, I want to use the same glibc what the application is
> compiled against.
>
>
Hi Richard,
After adding some new ops, I can keep the conditional compare to the
end of tree-level optimization. As tests, I expand conditional compare
to BIT_AND_EXPR/BIT_IOR_EXPR, which still depend on later "combine"
pass to combine them.
Is it possible to expand it to *cmp_and/*cmp_ior like p
== Issues ==
* None
== Progress ==
* Run native regression tests for conditional compare on Pandaborad ES.
- Fix several front-end issue to handle conditional compare in error message.
== Plan ==
* Continue on conditional compare.
* Linaro toolchain 2013.05 binary release.
Best Regards!
-Zh
== Issues ==
* None
== Progress ==
* Continue on conditional compare.
- Mix fixes for bootstrap.
* Update shrink-wrap patches according to comments and retest them on
Pandaboard and Chromebook.
* Prebuild 2013.05 Linaro toolchain locally.
- gdb related local patches need rework.
== Plan =
ild:
-marm -march=armv4t -mfloat-abi=soft
* Conditional compare.
- Investigate vrp pass to simplify conditional compare.
- Investigate reassoc pass to handle conditional compare
- All experimental codes are pushed to
lp:~zhenqiang-chen/gcc-linaro/4.8-conditional-compare
* Fix binary relea
== Issues ==
* None
== Progress ==
* 3 day off holiday.
* Investigate uninit1 pass to handle conditional compare.
* Investigate lp:1173300 and lp:1174350.
== Plan ==
* Continue on conditional compare.
Best Regards!
-Zhenqiang
___
linaro-toolchain m
On 30 April 2013 01:32, Kalai Narayanan-SSI wrote:
> Hi,
> I'm trying to build the aarch64 tool chain from source on a Redhat machine.
> I see that build.mk in the crosstool package requires a few .deb packages. If
> I want to build this on a Redhat machine, what are the changes I have to do?
Summary:
* Enhance Linaro crosstool-ng.
Details:
1. Work with Bero to release 4.8 binary build.
2. Update Linaro crosstool-ng to use ISL/CLooG for 4.8 build (lp:1172595).
3. Rebase conditional compare experimental codes to lp:gcc-linaro/4.8.
Plan:
* Investigate the impact of conditional compare o
1 - 100 of 198 matches
Mail list logo
