- linaro-toolchain - lists.linaro.org

[ACTIVITY] 21-24 May 2013

by Kugan

== Progress == VRP based zero/sign extension - Got some review comments for the patch and started addressing them - split the patch into two; 1. propagating value range and 2. do rtl expansion - testing in progress specfp regression - Benchmarked spec2k for A15 with trunk and couldn't reproduce it. - benchmarked spec2k for A9 with trunk and couldn't reproduce between 24th and 28th == Leave == - Monday off Sick == Plan == VRP based zero/sign extension - Send patch for review specfp regression - benchmark for trunk version on 23rd - Resolve regression

13 years, 2 months

1
0
0 0

[ACTIVITY] May 6-24

by Rob Savoye

Sorry, this covers the last two weeks, not just one. == Progress == * Created database schema for DejaGnu test results * Created data schema for benchmarks * Wrote scripts to convert benchmark and test data into a form that can be imported into a database, added them to DejaGnu branch * Imported all historical benchmark data * Imported most historical test results (GCC still importing) * Did some experimental graphs of test results * Read lots of web pages to come up to speed on Linaro, registered for lots of web pages and accounts * Learned about Cbuild and LAVA * Started on Cbuild v2 * Installed Ubuntu on Chromebook == Plan == * Write Cbuild 2 design doc * Continue work on Cbuild v2 to be able to use it for the June release * Get remote testing working with Chromebook & foundation model * More support tasks resulting from move off launchpad - rob -

13 years, 2 months

1
0
0 0

Debugging in Eclipse

by Paul CLaessen

Greetings, I'm using the Linaro tool chain with Eclipse (Juno) (under Windows) and openOCD to write firmware for an STM32F20x based design (using an ST-Link2 debugger). In general, that all works fairly well. The part I'm having problems with is debugging (step-in, etc) from Eclipse. The execution flow seems chaotic when single stepping through C code: it skips statements, it jumps into the middle of a function, then returns to the start of a function, it loops over certain statements (while there's no loop in the code), etc. (It's close to useless). I have seen this behavior with other IDE's and tool chains when code was built with optimization turned on. However, I specify 'no optimization' (-O0) when I build my code. My questions: a) Is there some implicit optimization being done in the compiler, even though I tell it not to do so, which may affect proper debugging? b) Are other people using Eclipse (Juno) and are they seeing the same issue? Are there any known ways to fix this chaotic debugger behavior? Kind regards, ~ Paul Claessen

13 years, 2 months

2
1
0 0

[ACTIVITY] Week 21

by Will Newton

== Progress == * binutils on ARM testsuite finally green in cbuild! * Tested and pushed to gerrit bionic memcpy patches. * Investigated binutils native AArch64 testsuite failures (not IFUNC related). * Made a start on the DeveloperTools/LibraryPerformance wiki. * Started looking at the Android memcpy problem on Galaxy Nexus. == Issues == * binutils make ; make check takes over 24 hours on foundation model! == Plan == * Respin AArch64 IFUNC binutils patch once relocation number allocated. * Setup git mirrors for binutils, glibc and newlib. * Android memcpy issue. -- Will Newton Toolchain Working Group, Linaro

13 years, 2 months

1
0
0 0

[ACTIVITY] 20-24 May 2013

by Christophe Lyon

== Progress == * Disable-peeling: looking at how to have less aggressive vectorization * Libsanitizer/aarch64: initiated upstream discussion * PGO/LTO bug reported by Doko: SD card too small to reproduce the problem * Merges for linaro-gcc-2013.06: started looking at what to backport, started merges * Jira/wiki: started cleanup/collecting new cards * Internal support == Next == * Jira: update status on cards/blueprints backported from launchpad * Merges for linaro-gcc-2013.06: continue collecting relevant merges * Disable-peeling: continue investigating vectorizer behaviour *Libsanitizer/aarch64: look at frame implementation * PGO/LTO: complete build of python * Neon intrinsics: continue improving crc with vuzp/veor

13 years, 2 months

1
0
0 0

[ACTIVITY] report week 21

by Peter Maydell

Progress: * misc ** got raring/aarch64 cross build set up ** reducing number of places that need changing for a new qemu target: sent some simple configure patches ** some 32 bit cleanup work that will help with getting John's AArch64 patches to work ** tested Huawei's aarch64 patches and confirmed they work ** rebased qemu-linaro (and passed the results to Serge H for Ubuntu) ** sent patches which make QEMU builds for arm/ppc/microblaze guests require libfdt, since a non-FDT-aware ARM QEMU is becoming rapidly less and less useful Plans: * handover from John Rigby * VIRT-55: talk to Andre about testing; investigate testing migration using LAVA * set up a new qemu-linaro tree/branch as our CI/LAVA input [to keep it separate from our "we release this" tree] * restart work on upstreaming omap3 patches as part of my generic qemu maintenance work (will reduce our maintenance burden in the long term) -- PMM

13 years, 2 months

1
0
0 0

[ACTIVITY] Week 21

by Renato Golin

== Progress == * Buildbots - Self-hosting bot online - Fiddling with MCJIT tests to get bots green * Benchmarks - Running Phoronic benchmarks: GCC vs. LLVM, good results - Got a sample of the PerfDB SQLite database, writing some queries * Jira/Wiki farming - Creating loads of new cards, blueprints, sub-tasks - Adding content to the wiki pages about processes, cards, etc * Release 3.3 - RC2 is out, no regressions, already on official repository * EuroLLVM 2013 - Monthly call, wrap-up, preview of next year's == Plan == * Try running a CBuild benchmark with LLVM 3.3 (Rob?) * Automate release process, maybe we can do that every month * Automate Phoronix test (GCC+LLVMrel+LLVMsvn) * Follow up on Panda/Arndale ordering, needed for buildbots * Try to extract useful information from perf database

13 years, 2 months

1
0
0 0

help fighting with optimizations

by Michael Hudson-Doyle

Hi all, I've spent a little while porting an optimization from Python 3 to Python 2.7 (http://bugs.python.org/issue4753). The idea of the patch is to improve performance by dispatching opcodes on computed labels rather than a big switch -- and so confusing the branch predictor less. The problem with this is that the last bit of code for each opcode ends up being the same, so common subexpression elimination wants to coalesce all these bits, which neatly and completely nullifies the point of the optimization. Playing around just building from source directly, it seems that -fno-gcse prevents gcc from doing this, and the resulting interpreter shows a small performance improvement over a build that does not include the patch. However, when I build a debian package containing the patch, I see no improvement at all. My theory, and I'd like you guys to tell me if this makes sense, is that this is because the Debian package uses link time optimization, and so even though I carefully compile ceval.c with -fno-gcse, the common subexpression elimination happens anyway at link time. I've tried staring at disassembly to confirm or deny this but I don't know ARM assembly very well and the compiled function is roughtly 10k instructions long so I didn't get very far with this (I can supply the disassembly if someone wants to see it!). Is there some way I can tell GCC to not compile perform CSE on a section of code? I guess I can make sure that the whole program, linker step and all, is compiled with -fno-gcse but that seems a bit of a blunt hammer. I'd also be interested if you think this class of optimization makes little sense on ARM and then I'll stop and find something else to do :-) Cheers, mwh

13 years, 2 months

3
3
0 0

Semi-hosting on v8 Foundation Model using gnu tools

by Padgett Don-B43265

The v8 Foundation Model User Guide has a bare metal hello world example that uses semi-hosting. The Makefile uses ARM tools, however. Is there equivalent support for this example using a bare metal version of the gnu tools, such as gcc-linaro-aarch64-none-elf-4.8-2013.04-20130422_linux.tar.xz? I took a look, but didn't see a way to do this. Of course, running the Linaro linux port on the v8 Foundation Model allows one to run hello world and much more, but I'm currently only interested in a bare metal target using gnu tools. Thanks, Don

13 years, 2 months

3
3
0 0

[ACTIVITY] 13 - 17 May 2013

by Omair Javaid

== Progress == * Backed up laptop data and did new ubuntu installation which crashed for some reason. * Wrote python script with googledoc API to automate fill up of googlespread sheet. * Created and tested patch for arm assembler compatibility fixes for gdb.dwarf test suite assembly files. == Plan == * Identify arm bugs out of gdb7.6 test results and work towards fixing them. * Update JIRA enteries with test suite failures on arm to track progress. * More work on automating googledoc spreadsheet writing using python. * 2 Day off on coming Friday and Monday.

13 years, 2 months

1
0
0 0

[ACTIVITY] 13 May - 17 May 2013

by Venkataramanan Kumar

== Progress == * AARCH64 - gprof support. Completed gprof -c support for aarch64. Got reviewed internally by Matt and Will. Patch yet to be posted. Waiting for some feedback on copyright message. *Testing GCC bootstrap and regression suite. Created a large image with help of Bero. Bootstrap fails with GCC trunk libgcc_eh.a (unwind-dw2-fde-dip.o) hidden symbol __register_frame_info is referenced bu DSO ld final link Bad value. Drilling down == Plan == * Post patches in gcc and binutils for gprof work * Continue handling builtin_return_address when -fomit-frame-pointer is enabled. * Continue gcc bootstrap and regression test.

13 years, 2 months

1
0
0 0

[ACTIVITY] Week 20

by Yvan Roux

== Issues == * Cbuild down most of the week. == Progress == * 4.6 and 4.7 releases - Released after a painful week ! * LRA on ARM and AArch64: - Enabled on AArch64, but it leads to an ICE too. - Applied Brice's ARM patches didn't solved the issue. - Looked at the documentation/comments to understand the process. - Debug ongoing. == Plan == * Continue on LRA

13 years, 2 months

1
0
0 0

[ACTIVITY] Week 20

by Zhenqiang Chen

== 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 == * Continue on conditional compare to bootstrap. * Linaro toolchain 2013.05 binary release. Best Regards! -Zhenqiang

13 years, 2 months

1
0
0 0

[ACTIVITY] 13-17 May 2013

by Kugan

== Progress == http://cards.linaro.org/browse/TCWG-13 - Resolved http://cards.linaro.org/browse/TCWG-14 - Modified patch Posted upstream for review == Plan == http://cards.linaro.org/browse/TCWG-14 - Address and review comments http://cards.linaro.org/browse/TCWG-55 - Reproduce it and find the reason for specfp regression

13 years, 2 months

1
0
0 0

[ANNOUNCE] Linaro GDB 7.6 2013.05 released

by Matthew Gretton-Dann

The Linaro Toolchain Working Group is pleased to announce the release of Linaro GDB 7.6. Linaro GDB 7.6 2013.05 is the first release in the 7.6 series. ***NOTE*** Linaro GDB 7.6 2013.05 is identical to the FSF GDB 7.6 release, except for the change in version number and Linaro branding, since all Linaro GDB features were already accepted upstream and are included in the FSF release as-is. Future releases in the Linaro GDB 7.6 series may include additional ARM-focused bug fixes and enhancements. The source tarball is available at: https://launchpad.net/gdb-linaro/+milestone/7.6-2013.05 More information on Linaro GDB is available at: https://launchpad.net/gdb-linaro -- Matthew Gretton-Dann Linaro Toolchain Working Group matthew.gretton-dann(a)linaro.org

13 years, 2 months

1
0
0 0

[ANNOUNCE] Linaro GCC 4.8, 4.7 and 4.6 2013.05 released

by Yvan Roux

The Linaro Toolchain Working Group is pleased to announce the 2013.05 release of Linaro GCC 4.8, Linaro GCC 4.7 and Linaro GCC 4.6. Linaro GCC 4.8 2013.05 is the second release in the 4.8 series. Based off the latest GCC 4.8.0+svn198615 release, it includes performance improvements and bug fixes. Interesting changes include: * Updates to GCC 4.8.0+svn198615 * Backport of support for prologue/epilogues using LDRD and STRD in ARM mode * Backport of support for further AArch64 instructions * Backport of support for further ARMv8 AArch32 instructions. Linaro GCC 4.7 2013.05 is the fourteenth release in the 4.7. Based off the latest GCC 4.7.3+svn198701 release, this is the first release after entering maintenance. Interesting changes include: * Updates to GCC 4.7.3+svn198701 * Includes arm/aarch64-4.7-branch up to svn revision 198689 Linaro GCC 4.6 2013.05 is the 27th release in the 4.6 series. Based off the latest GCC 4.6.4+svn197894 release, this is the fourteenth release after entering maintenance and the final one. Interesting changes include: * Updates to 4.6.4+svn197894 The source tarball is available from: https://launchpad.net/gcc-linaro/+milestone/4.8-2013.05 https://launchpad.net/gcc-linaro/+milestone/4.7-2013.05 https://launchpad.net/gcc-linaro/+milestone/4.6-2013.05 Downloads are available from the Linaro GCC page on Launchpad: https://launchpad.net/gcc-linaro More information on the features and issues are available from the release page: https://launchpad.net/gcc-linaro/4.8/4.8-2013.05 https://launchpad.net/gcc-linaro/4.7/4.7-2013.05 https://launchpad.net/gcc-linaro/4.6/4.6-2013.05 Mailing list: http://lists.linaro.org/mailman/listinfo/linaro-toolchain Bugs: https://bugs.launchpad.net/gcc-linaro/ Questions? https://ask.linaro.org/ Interested in commercial support? Inquire at support(a)linaro.org

13 years, 2 months

1
0
0 0

[ACTIVITY] Week 20

by Renato Golin

== Progress == * 3.3 Release - Bootstrapping, testing, fixing bugs, etc. - RC1 released on Tuesday http://people.linaro.org/~rengolin/llvm/ - Fix for C11 atomics on Linux http://llvm.org/bugs/show_bug.cgi?id=15429 - Fix for zero extend vector bug in test-suite http://llvm.org/bugs/show_bug.cgi?id=15970 * Test-Suite - ClamAV fails on Calxeda, same as PPC64 (bad test) * Self-Host Buildbot - Re-purposing the Panda back to buildbot service - Buildbot passing green, setting it up on Build Master == Issues == Calxeda gets turned off quite regularly, which messes up any long term commitment you might have for them. == Plan == * Install Ubuntu on Chromebook, run benchmarks with 3.3 RC1 * Try to revive LLVM CBuild job if it's any different than our current buildbot * Try to setup benchmark jobs for LLVM, either buildbots, CBuild, or whatever * Stay alert for RC2 and re-run release process on them

13 years, 3 months

1
0
0 0

[ACTIVITY] Week 20

by Will Newton

== Progress == * Finished porting ld-ifunc tests to AArch64. * Requested a relocation number for R_AARCH64_IRELATIVE. * Tested AArch64 ifunc code natively to run generic ifunc tests. * Investigated gdb bug #1175525 and submitted workaround patch to gdb-patches. * Started DeveloperTools and LibraryPerformance wiki pages. * Submitted initial version of AArch64 binutils patch with temporary reloc number. == Issues == * None. == Plan == * Complete process of getting R_AARCH64_IRELATIVE allocated. * Feedback on binutils AArch64 ifunc patch. * Feedback on slightly hacky gdb patch. * bionic memcpy. -- Will Newton Toolchain Working Group, Linaro

13 years, 3 months

1
0
0 0

[ACTIVITY] 13-17 May 2013

by Christophe Lyon

== Progress == * Disable-peeling: analyzed regression on one bench. * Libsanitizer/aarch64: - porting will require more effort than aarch32. - some syscalls are not supported by aarch64 - libsanitizer expects frame to grow downwards (true on aarch32, false on aarch64) * PGO/LTO bug reported by Doko: updating board environment to reproduce it * Internal support == Next == * Disable-peeling: see how to disable too aggressive vectorization * Revert-coalesce-vars: discuss how to handle it with the team * Neon intrinsics: continue improving crc with vuzp * Neon intrinsics tests: handle feedback if any * PGO/LTO bug: reproduce it

13 years, 3 months

1
0
0 0

[ACTIVITY] report week 20

by Peter Maydell

Progress: * VIRT-49, VIRT-50 [cp15 migration, reset] ** last bits of patch cleanup complete; realised I could test KVM migration without any timer or vgic patches; did so and sent first version of patches out to qemu-devel * VIRT-55: ** started to draft basic notes on what we want to test: https://wiki.linaro.org/PeterMaydell/MigrationTesting * misc ** reviewed Huawei's aarch64 tcg target patches; there are some issues they need to fix but overall looking good ** fixed a last-minute bug in the versatilepb PCI controller model (some changes we made earlier in the release cycle wouldn't work with newer Linux kernels) Plans: * deal with any code review feedback on patchset * set up a raring/aarch64 cross build environment (got partway through this, waiting for wookey to update some packages) * more in-depth review/test of John Rigby's mach-virt, aarch64 patchsets * VIRT-55: write up how to test migration (and talk to Andre about what he's doing testing-wise) -- PMM

13 years, 3 months

1
0
0 0

hot spot on the vsub.f32 instruction

by YongQin Liu

Hi, All The attachment file is analysed by the streamline tool. How to do you think about the vsub.f32 hot spot there? Is there any way we can improve that? -- Thanks, Yongqin Liu --------------------------------------------------------------- #mailing list linaro-android(a)lists.linaro.org <linaro-dev(a)lists.linaro.org> http://lists.linaro.org/mailman/listinfo/linaro-android linaro-validation(a)lists.linaro.org <linaro-dev(a)lists.linaro.org> http://lists.linaro.org/pipermail/linaro-validation

13 years, 3 months

6
9
0 0

[ACTIVITY] 6 - 10 May 2013

by Omair Javaid

== Progress == * Filled up the googledoc comparison sheets of gdb 7.6 test suite run in different configuration on chromebook and x86. * Filled up the googledoc comparison sheets of gdb 7.5.1 test suite run in different configuration on chromebook and x86. * Compared GDB 7.6 and 7.5.1 results which show good improvements in gdb 7.6. == Plan == * Repair my laptop's ubuntu installation which crashed for some reason. * Submit patch to fix dwarf test suite in gdb 7.6 * Investigate gdb 7.6 gdb.base failures on arm and try to figure out causes + possible solution. * Try to figure out a way automate a comparison of two test suite results and upload them to googledocs.

13 years, 3 months

1
0
0 0

bitbake linaro-image-sdk fails on 13.04

by Aparna Mandke

Hi, I downloaded 13.04 version and tried to compile linaro-image-sdk and linaro-image-lamp. Both these builds fail with the following error. However, I could compile core-image-minimum. Can somebody help me with this issue? Is there any quick workaround. Mostly, I do not need ltp package. Thanks, Aparna aarch64-oe-linux-gcc -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed --sysroot=/home/kvs/aparna/openembedded/build/tmp-eglibc/sysroots/genericarmv8 -O2 -pipe -g -feliminate-unused-debug-types -g -O2 -fno-strict-aliasing -pipe -Wall -DTST_USE_NEWER64_SYSCALL=1 -I/home/kvs/aparna/openembedded/build/tmp-eglibc/work/aarch64-oe-linux/ltp/20120903-r2/ltp-20120903/testcases/kernel/include -I/home/kvs/aparna/openembedded/build/tmp-eglibc/work/aarch64-oe-linux/ltp/20120903-r2/ltp-20120903/testcases/kernel/syscalls/getdents -I/home/kvs/aparna/openembedded/build/tmp-eglibc/work/aarch64-oe-linux/ltp/20120903-r2/ltp-20120903/testcases/kernel/syscalls/getdents/../utils -I../../../../include -I../../../../include -D_FILE_OFFSET_BITS=64 -DOFF_T=__off64_t -c -o getdents04_64.o getdents04.c | In file included from getdents01.c:57:0: | getdents.h: In function 'getdents': | getdents.h:60:16: error: 'SYS_getdents' undeclared (first use in this function) | getdents.h:60:16: note: each undeclared identifier is reported only once for each function it appears in | In file included from getdents02.c:53:0: | getdents.h: In function 'getdents': | getdents.h:60:16: error: 'SYS_getdents' undeclared (first use in this function) | getdents.h:60:16: note: each undeclared identifier is reported only once for each function it appears in | In file included from getdents03.c:56:0: | getdents.h: In function 'getdents': | getdents.h:60:16: error: 'SYS_getdents' undeclared (first use in this function) | getdents.h:60:16: note: each undeclared identifier is reported only once for each function it appears in | In file included from getdents04.c:56:0: | getdents.h: In function 'getdents': | getdents.h:60:16: error: 'SYS_getdents' undeclared (first use in this function) | getdents.h:60:16: note: each undeclared identifier is reported only once for each function it appears in | make[4]: *** [getdents01] Error 1 | make[4]: *** Waiting for unfinished jobs.... | make[4]: *** [getdents02] Error 1 | In file included from getdents03.c:56:0: | getdents.h: In function 'getdents': | getdents.h:60:16: error: 'SYS_getdents' undeclared (first use in this function) | getdents.h:60:16: note: each undeclared identifier is reported only once for each function it appears in | make[4]: *** [getdents03] Error 1 | In file included from getdents02.c:53:0: | getdents.h: In function 'getdents': | getdents.h:60:16: error: 'SYS_getdents' undeclared (first use in this function) | getdents.h:60:16: note: each undeclared identifier is reported only once for each function it appears in | make[4]: *** [getdents04] Error 1 | make[4]: *** [getdents03_64.o] Error 1 | In file included from getdents04.c:56:0: | getdents.h: In function 'getdents': | getdents.h:60:16: error: 'SYS_getdents' undeclared (first use in this function) | getdents.h:60:16: note: each undeclared identifier is reported only once for each function it appears in | In file included from getdents01.c:57:0: | getdents.h: In function 'getdents': | getdents.h:60:16: error: 'SYS_getdents' undeclared (first use in this function) | getdents.h:60:16: note: each undeclared identifier is reported only once for each function it appears in | make[4]: *** [getdents02_64.o] Error 1 | make[4]: *** [getdents04_64.o] Error 1 | make[4]: *** [getdents01_64.o] Error 1 | make[4]: Leaving directory `/home/kvs/aparna/openembedded/build/tmp-eglibc/work/aarch64-oe-linux/ltp/20120903-r2/ltp-20120903/testcases/kernel/syscalls/getdents' | make[3]: *** [all] Error 2 | make[3]: Leaving directory `/home/kvs/aparna/openembedded/build/tmp-eglibc/work/aarch64-oe-linux/ltp/20120903-r2/ltp-20120903/testcases/kernel/syscalls' | make[2]: *** [all] Error 2 | make[2]: Leaving directory `/home/kvs/aparna/openembedded/build/tmp-eglibc/work/aarch64-oe-linux/ltp/20120903-r2/ltp-20120903/testcases/kernel' | make[1]: *** [all] Error 2 | make[1]: Leaving directory `/home/kvs/aparna/openembedded/build/tmp-eglibc/work/aarch64-oe-linux/ltp/20120903-r2/ltp-20120903/testcases' | make: *** [testcases-all] Error 2 | ERROR: oe_runmake failed | ERROR: Function failed: do_compile (see /home/kvs/aparna/openembedded/build/tmp-eglibc/work/aarch64-oe-linux/ltp/20120903-r2/temp/log.do_compile.6470 for further information) ERROR: Task 349 (/home/kvs/aparna/openembedded/openembedded-core/meta/recipes-extended/ltp/ ltp_20120903.bb, do_compile) failed with exit code '1'

13 years, 3 months

2
1
0 0

[ACTIVITY] 6 - 10 May 2013

by Kugan

== Done == http://cards.linaro.org/browse/TCWG-14 - Posted patch upstream for review http://cards.linaro.org/browse/TCWG-55 - benchmarking ongoing with git bisect http://cards.linaro.org/browse/TCWG-14 - Discussed the results with ARM maintainers and pinged the original patch. == Plan == http://cards.linaro.org/browse/TCWG-55 - Find the reason for spec2k fp performance regression. http://cards.linaro.org/browse/TCWG-14 - plan action based on review.

13 years, 3 months

1
0
0 0

[ACTIVITY] 6 May - 12 May 2013

by Venkataramanan Kumar

== Progress == * AARCH64 - gprof support. Submitted GCC patches to generate profile call. Also applied the review comments from Marcus and tested patches for aarch64-none-elf. http://gcc.gnu.org/ml/gcc-patches/2013-05/msg00597.html * Setup a Ubuntu machine at Office. Ran GCC testsuite with on openembeded/V8 model ref: http://people.linaro.org/~hrw/oe/vekumar/. This image has updated gcc and glibc and enables gprof. During bootstrap GCC build failed due to space getting over. Need to create a larger image. * Looking at how to handle builtin_return_address when -fomit-frame-pointer is enabled. GCC saves frame pointer for the function alone where builtin_return_address is used. Callers of the function may not have set up the frame yet. == Plan == * Continue gprof "-c" option support in binutils * Continue handling builtin_return_address when -fomit-frame-pointer is enabled. * Continue gcc bootstrap and regression suite after creating a larger image.

13 years, 3 months

1
0
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain