I have run the test on ARM on a number of toolchains, and confirmed that there
is no failure in that case.
The note:
note: variable tracking size limit exceeded with -fvar-tracking-assignments,
retrying without is present but does not lead to the memory error.
Michael will now help out in
Thank you for the bug report.
The comments above clarifies that the problem is that the functions
getcontext and setcontext is not supported for ARM.
I've set this ticket to medium priority for now. As stated by Peter
above, getting the functions into eglibc has already been recognized as
a
Thank you for the bug report. I've confirmed this with gcc-
linaro-4.6-2012.02 on ARM:
/home/asa-san/bugs/cbuild/slaves/ursa4/gcc-linaro-4.6-2012.02 gfortran -c -O1
-fpermissive -Wfatal-errors -w fbasics_gss-min.f
fbasics_gss-min.f: In function 'deval':
fbasics_gss-min.f:39:0: internal compiler
This ticket appears to be the same as:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52294.
a case where gcc generates a cbz instruction that ends up trying to reach too
far.
Attaching the assembly file mp.s generated with:
asa-san@ursa4:~/bugs/mp$
Hi Michael,
I cant' find any
asm
chunks in there.
(Only in some external declarations.)
Can it look any other way?
/Åsa
On 15 February 2012 22:39, Michael Hope 926...@bugs.launchpad.net
wrote:
Asa, does the code contain any inline assembly? GCC estimates the size
of each instruction and
Thank you for the bug report. I've confirmed this with gcc-
linaro-4.6-2012.01 on ARM:
asa-san@ursa4:~/bugs/mp$
/scratch/asa-san/cbuild/slaves/ursa4/gcc-linaro-4.6-2012.01/gcc-binary/bin/gcc
-c -o mp.o mp.c -O3 -funroll-loops
/tmp/ccv0lfQ5.s: Assembler messages:
/tmp/ccv0lfQ5.s:116: Error:
