The Cygwin folks have an issue that GCC-4.6.3 doesn't compile ECL
properly due to a GCC bug
(http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52061).
Since this problem doesn't seem to occur with GCC-4.7.2, I would propose
to upgrade Sage's GCC to version 4.7.2. There already exists an optional
On Thursday, March 7, 2013 4:38:37 AM UTC-5, Jeroen Demeyer wrote:The Cygwin folks have an issue that GCC-4.6.3 doesn't compile ECL
properly due to a GCC bug
(http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52061).
Since this problem doesn't seem to occur with GCC-4.7.2, I would propose
to upgrade Sage's GCC to version 4.7.2. There already exists an optionalI assume this would mostly be to avoid the need to install not just gcc, but g++ and gfortran on Cygwin? Otherwise it hardly seems worth the effort. Given that we aren't intending for most Cygwin folks to have to actually build from source, maybe this isn't necessary. Alternately, the default Cygwin install seems to come with gcc3, and perhaps that could be used to build the Sage gcc package... I guess it would be interesting to hear more about this. How does the gcc-4.7 spkg do on various Mac systems?
How does the gcc-4.7 spkg do on various Mac systems?
Jeroen Demeyer wrote:
> The Cygwin folks have an issue that GCC-4.6.3 doesn't compile ECL
> properly due to a GCC bug
> (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52061).
>
> Since this problem doesn't seem to occur with GCC-4.7.2, I would propose
> to upgrade Sage's GCC to version 4.7.2. There already exists an optional
> package for this, so basically we just need to make that optional
> package standard. Several of the buildbots are already using GCC-4.7.x
> or even GCC-4.8-trunk, so GCC-4.7.x should be well-tested by now and I
> don't expect problems. If nobody complains, I will do this upgrade to
> GCC-4.7.2.
Just for the record, I get ICEs with the GCC 4.7.2.p0 spkg (with Sun as
and ld) on Solaris SPARC (32-bit) when compiling GAP and libGAP with
-O3; -O2 works in both cases. (I didn't get them with the system-wide
GCC 4.7.0 on {mark,mark2}.)
Jean-Pierre Flori wrote:
> On Saturday, March 30, 2013 7:15:10 AM UTC+1, leif wrote:
> Just for the record, I get ICEs with the GCC 4.7.2.p0 spkg (with Sun as
> and ld) on Solaris SPARC (32-bit) when compiling GAP and libGAP with
> -O3; -O2 works in both cases. (I didn't get them with the system-wide
> GCC 4.7.0 on {mark,mark2}.)
>
> I cannot reproduce these on the Solaris I have access to (same as the
> one with singular/restrict problem).
> With Sage 5.7 and the GCC 4.7.2.p1 spkg (not that it should not make any
> difference), I can build the GAP and libgap spkgs both with CFLAGS unset
> and with CFLAGS="-O3".
I also built GCC itself with -O3 (and -mcpu=ultrasparc3
-mtune=ultrasparc3); not yet sure whether that matters.
On Saturday, March 30, 2013 2:46:56 PM UTC+1, leif wrote:Jean-Pierre Flori wrote:
> On Saturday, March 30, 2013 7:15:10 AM UTC+1, leif wrote:
> Just for the record, I get ICEs with the GCC 4.7.2.p0 spkg (with Sun as
> and ld) on Solaris SPARC (32-bit) when compiling GAP and libGAP with
> -O3; -O2 works in both cases. (I didn't get them with the system-wide
> GCC 4.7.0 on {mark,mark2}.)
>
> I cannot reproduce these on the Solaris I have access to (same as the
> one with singular/restrict problem).
> With Sage 5.7 and the GCC 4.7.2.p1 spkg (not that it should not make any
> difference), I can build the GAP and libgap spkgs both with CFLAGS unset
> and with CFLAGS="-O3".
I also built GCC itself with -O3 (and -mcpu=ultrasparc3
-mtune=ultrasparc3); not yet sure whether that matters.I rebuilt GCC with CFLAGS="-O3 -mcpu=niagara2 -mtune=niagara2".
And ... tada! It breaks when building GAP:
{{{
../../src/blister.c: In function 'InitKernel':
../../src/blister.c:2743:1: internal compiler error: in simplify_immed_subreg, at simplify-rtx.c:5262
}}}
three times.