there are many major Sage components that do not build natively on Windows, e.g. GAP, and where native ports are not on roadmaps of the corresponding development teams. Other platforms might have a better chance, e.g. GAP is very compiler- tolerant (as there is no C++ there).
Dima On Jul 16, 10:42 am, Peter Jeremy <[email protected]> wrote: > On 2010-Jul-16 10:48:15 +0200, William Stein <[email protected]> wrote: > > >worked". This wouldn't be likely with Microsoft's own compilers... > >For starters, the Singular developers don't work with those compilers, > >so the Singular devs will make all kinds of code changes, which would > >then have to be ported/fixed. > > As has been discussed previously, this effort is worthwhile in any > case. Firstly, gcc does not generate especially good SPARCv9 or iA64 > code - being able to use vendor compilers is likely to provide a boost > to Sage performance on those platforms. Secondly, the different checks > performed by different compilers are likely to turn up in Sage code and > correcting them will improve the reliability and robustness of Sage. > > -- > Peter Jeremy > > application_pgp-signature_part > < 1KViewDownload -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
