[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Building snapshot versions for Windows
From: |
Clemens Buchacher |
Subject: |
Re: Building snapshot versions for Windows |
Date: |
Sat, 11 May 2013 12:40:08 +0200 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Thu, May 09, 2013 at 11:02:44AM +0200, Clemens Buchacher wrote:
>
> $ tmp-gcc/gcc-4.7.2.build/./gcc/xgcc [...] tmp-gcc/gcc-4.7.2/libgcc/libgcc2.c
> /home/drizzd/src/mxe-octave/tmp-gcc/gcc-4.7.2/libgcc/libgcc2.c: In function
> '__absvdi2':
> /home/drizzd/src/mxe-octave/tmp-gcc/gcc-4.7.2/libgcc/libgcc2.c:273:1:
> internal compiler error: Segmentation fault
I could reduce this to a simple testcase:
$ cat libgcc2-mod.c
typedef int DItype __attribute__ ((mode (DI)));
typedef unsigned int UDItype __attribute__ ((mode (DI)));
DItype __absvDI2 (DItype a)
{
DItype w;
if (a < 0)
w = -(UDItype) a;
return w;
}
EOF
$ gcc-4.7.2.build/gcc/xgcc -Bgcc-4.7.2.build/gcc -O2 -c libgcc2-mod.c
-save-temps
libgcc2-mod.c: In function '__absvDI2':
libgcc2-mod.c:12:1: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
But since I do not have this issue with gcc 4.8.0, I do not know if it's
worth investigating any furhter. Upstream mxe has already updated to gcc
4.8.0. I only need to patch mexproto.h on top of that because of bug
#38746 and I should be good to go.
If you like I can also cherry-pick other relevant package updates for
gcc dependencies from mxe upstream.
Can we do that instead, or do we have some incentive to keep gcc 4.7.2?
Clemens