[ACTIVITY] Week 13
== Progress == o Extended validation (7/10) * Fixed and improved extended native validation * Discussed proposed patch in dejagnu on process killing mechanism * Testing a fix/workaround in GCC guality tests * Re-implemented and tested fix for dejagnu remote layout o Misc (3/10) * Various meetings == Plan == o Continue on extended validation o Finalize DejaGNU patches, GCC ARMv8.1 builtins fix. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Question regarding the arm gcc 5.3 to build android
Hi Christophe, On 2016/4/4 3:58, Christophe Lyon wrote: On 1 April 2016 at 12:04, Ramana Radhakrishnan wrote: On 31/03/16 18:26, Jim Wilson wrote: On Thu, Mar 31, 2016 at 5:12 AM, fengwei.yin wrote: Because gcc 4.9 could build this file without any issue, I apply --save-temps with gcc 4.9. The ii file is attached. Can't see significant differences. There is a patch in gcc-5 to make unified assembler syntax the default. Unfortunately, it changes how extended asms work, which is perhaps a bug. The message claims it doesn't affect extended asms, but it does. https://gcc.gnu.org/ml/gcc-patches/2015-11/msg01196.html The interesting bit is the change to ASM_APP_OFF. This is now https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70496 for FSF trunk. Sorry about the breakage. Ramana As Ramana fixed it promptly on trunk, we'll backport it and it will be available in our next linaro-gcc-5.x snapshot. Thanks a lot. I will try once the next snapshot is ready. Regards Yin, Fengwei Thanks, Christophe. gcc-4.9 emits a .thumb after the extended asm to switch back into thumb mode just in case. gcc-5.3 instead emits .syntax unified, which doesn't change the arm/thumb mode, just the syntax supported. This is arguably a bug, but this doesn't immediately help you. It could take a little time to get gcc-5.x source fixed, and then the compiler binary releases. Or alternatively we could fix the asm to work with gcc 5. Jim ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Cross compilation issue
On Sat, Apr 2, 2016 at 3:00 AM, $rik@nth wrote: > /home/hydlnxbld84/Srikanth/abe/build/snapshots/gcc.git~linaro-gcc-5-branch/gcc/real.h:79:76: > error: size of array test_real_width is negative >[sizeof (REAL_VALUE_TYPE) <= REAL_WIDTH * sizeof (HOST_WIDE_INT) ? 1 : -1]; I don't know offhand how one can get this error. You'd have to look at the preprocessor output here and try to figure out what wrong with this calculation. Maybe you accidentally used --build x86_64-linux-gnu on a 32-bit machine? Jim ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Cross compilation issue
On Fri, Apr 1, 2016 at 7:10 AM, $rik@nth wrote: > I've read the Wiki page and start using abe tool to build cross > compile for ARM on x86 build system. But i am getting below error. > Also --set arch=arm argument is showing the arch is not found while > configuring. Abe --set arch= translates into a gcc -march= option. arm isn't a valid argument for that in an arm toolchain. A valid choice would be armv7-a for instance. But you shouldn't need an abe arch option normally. Only if you want a different -march= to be the default. > /local2/mnt/tools/Linux-kernel/Linaro-GCC/abe/build/snapshots/gcc.git~linaro-gcc-5-branch/libgcc/libgcc2.c:59:1: > error: __fixdfdi undeclared here (not in a function) > /local2/mnt/tools/Linux-kernel/Linaro-GCC/abe/build/snapshots/gcc.git~linaro-gcc-5-branch/libgcc/libgcc2.c:59:1: > error: __aeabi_d2lz defined both normally and as âaliasâ attribute > /local2/mnt/tools/Linux-kernel/Linaro-GCC/abe/build/snapshots/gcc.git~linaro-gcc-5-branch/libgcc/libgcc2.c:59:3: > warning: parameter names (without types) in function declaration > [enabled by default] > /local2/mnt/tools/Linux-kernel/Linaro-GCC/abe/build/snapshots/gcc.git~linaro-gcc-5-branch/libgcc/libgcc2.c:59:3: > warning: parameter names (without types) in function declaration > [enabled by default] > make[2]: *** [_fixdfdi.o] Error 1 It isn't obvious what went wrong here. Try looking at the preprocessor output of the failing gcc command. You didn't mention the abe command used here. It may take a little time to learn how to use abe to do a build. Abe tries to make builds easier, but it doesn't make them easy. I don't know if abe can be used to do what you want. The linaro toolchain group doesn't do canadian cross builds except for windows hosted builds, so we don't have any process to do what you want. There is a linaro group that builds OS releases that contain native gcc binaries. I think that they use Open Embedded, but I've never used Open Embedded, so I don't know how any of that works. Jim ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Cross compilation issue
On Mon, Apr 4, 2016 at 9:27 PM, Jim Wilson wrote: > On Sat, Apr 2, 2016 at 3:00 AM, $rik@nth wrote: >> /home/hydlnxbld84/Srikanth/abe/build/snapshots/gcc.git~linaro-gcc-5-branch/gcc/real.h:79:76: >> error: size of array test_real_width is negative >>[sizeof (REAL_VALUE_TYPE) <= REAL_WIDTH * sizeof (HOST_WIDE_INT) ? 1 : >> -1]; > > I don't know offhand how one can get this error. You'd have to look > at the preprocessor output here and try to figure out what wrong with > this calculation. Maybe you accidentally used --build > x86_64-linux-gnu on a 32-bit machine? I am issuing abe with `../abe.sh --set cflags="-static" --set ldflags="-pthread" --host arm-linux-gnueabi --target arm-linux-gnueabi --build all` am i configuring something wrong here? Please correct me > > Jim -- Thanks & Regards, M.Srikanth Kumar. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Cross compilation issue
On Mon, Apr 4, 2016 at 11:30 AM, $rik@nth wrote: > I am issuing abe with `../abe.sh --set cflags="-static" --set > ldflags="-pthread" --host arm-linux-gnueabi --target arm-linux-gnueabi > --build all` > am i configuring something wrong here? Please correct me That won't work without an arm-linux-gnueabi toolchain in the path. When I try to build an arm-linux-gnueabi toolchain by dropping the --host option, I get a glibc build failure home/wilson/Linaro/tcwg/X-tmp/builds/x86_64-unknown-linux-gnu/arm-linux-gnueabi/glibc.git~release-2.21-master/config.h:4:3: error: #error "glibc cannot be compiled without optimization" --set cflags is overriding the default flags instead of adding to them, so this isn't going to work. If I try using --set cflags="-O2 -static", then I get an abe option parse error ERROR (#612): check_directive (--stage requires a directive. abe.sh found the next -- switch. See --usage for details.' ) This is trying to parse -static thinking it is the abe --stage option because it accepts -sta* as an abbreviation. Personally, I think all of the abbreviations should be dropped as useless. Anyways, it seems it is ignoring the quotes when trying to parse the options. It appears that using the abe --set cflags option isn't useful, and you won't be able to build a static toolchain this way. I successfully built a cross by dropping the cflags and ldflags options. I then tried to use it to build a canadian cross. The build fails in gdb, complaining that I don't have a libtermcap library which is true. This is before it tried to build gcc, so I didn't get any gcc build. Jim ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] 27 March to 1 April 2016
== Progress == * Type promotion pass (4/10) - Tested many different architectures - Branch created - Getting ready to benchmark * LTO (2/10) - Read VRP algorithms - new - Discussing algorithm implementation * Bugs (1/10) - PR70359 * Misc (1/10) - GCC Lists - Jenkins benchmarking jobs * Public holiday (2/10) == Plan == * LTO and VRP ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Cross compilation issue
On Tue, Apr 5, 2016 at 6:44 AM, Jim Wilson wrote: > On Mon, Apr 4, 2016 at 11:30 AM, $rik@nth wrote: >> I am issuing abe with `../abe.sh --set cflags="-static" --set >> ldflags="-pthread" --host arm-linux-gnueabi --target arm-linux-gnueabi >> --build all` >> am i configuring something wrong here? Please correct me > > That won't work without an arm-linux-gnueabi toolchain in the path. > > When I try to build an arm-linux-gnueabi toolchain by dropping the > --host option, I get a glibc build failure > home/wilson/Linaro/tcwg/X-tmp/builds/x86_64-unknown-linux-gnu/arm-linux-gnueabi/glibc.git~release-2.21-master/config.h:4:3: > error: #error "glibc cannot be compiled without optimization" > --set cflags is overriding the default flags instead of adding to > them, so this isn't going to work. > > If I try using --set cflags="-O2 -static", then I get an abe option parse > error > ERROR (#612): check_directive (--stage requires a directive. abe.sh > found the next -- switch. See --usage for details.' ) Sure.. I will give it a try by looking more into the usage once to play with it. > This is trying to parse -static thinking it is the abe --stage option > because it accepts -sta* as an abbreviation. Personally, I think all > of the abbreviations should be dropped as useless. Anyways, it seems > it is ignoring the quotes when trying to parse the options. It > appears that using the abe --set cflags option isn't useful, and you > won't be able to build a static toolchain this way. > > I successfully built a cross by dropping the cflags and ldflags options. There is no way to build static tool chain by using abe tool at all? > > I then tried to use it to build a canadian cross. The build fails in > gdb, complaining that I don't have a libtermcap library which is true. > This is before it tried to build gcc, so I didn't get any gcc build. > > Jim -- Thanks & Regards, M.Srikanth Kumar. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Cross compilation issue
On Mon, Apr 4, 2016 at 8:18 PM, $rik@nth wrote: > There is no way to build static tool chain by using abe tool at all? Maybe modify abe/lib/make.sh to add -static directly to LDFLAGS? Jim ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
