mingw+gsl: bug and workaround

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

mingw+gsl: bug and workaround

Guido De Rosa
Hi!

There's a long-standing problem when building Gnu Scientific Library
(gsl) with MinGW:

http://lists.gnu.org/archive/html/bug-gsl/2006-09/msg00004.html

It might be a MinGW bug rather than a GSL one.

http://lists.gnu.org/archive/html/bug-gsl/2006-09/msg00005.html

Recently I found a temporary  workaround:

I manually edited a Makefile and changed/expanded  the -O2 option of
gcc with the long list of equivalent options:

        -fdefer-pop \
        -fmerge-constants \
        -fthread-jumps \
        -floop-optimize \

etc. etc.

according to http://gcc.gnu.org/onlinedocs/gcc-3.4.5/gcc/Optimize-Options.html

Surprisingly, after this change (that is supposed to change nothing)
'make check'  finally passed successfully the whole test suite.

More details here:

http://lists.gnu.org/archive/html/help-gsl/2009-01/msg00053.html

It seems a very subtle bug, indeed it makes it difficult to get a
native Windows port of a popular library such as the gsl.

Hope these info give some clue toward a fix...

--
Guido

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
MinGW-users mailing list
[hidden email]

You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users

_______________________________________________
This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.

Most annoying abuses are:
1) Top posting
2) HTML/MIME encoded mail
3) Improper quoting
4) Improper trimming
Reply | Threaded
Open this post in threaded view
|

Re: mingw+gsl: bug and workaround

Greg Chicares
On 2009-01-25 02:56Z, Guido De Rosa wrote:
>
> There's a long-standing problem when building Gnu Scientific Library
> (gsl) with MinGW:
>
> http://lists.gnu.org/archive/html/bug-gsl/2006-09/msg00004.html

Can you reduce this to a minimal, standalone testcase?

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
MinGW-users mailing list
[hidden email]

You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users

_______________________________________________
This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.

Most annoying abuses are:
1) Top posting
2) HTML/MIME encoded mail
3) Improper quoting
4) Improper trimming
Reply | Threaded
Open this post in threaded view
|

Re: mingw+gsl: bug and workaround

Guido De Rosa
2009/1/25 Greg Chicares <[hidden email]>:

> Can you reduce this to a minimal, standalone testcase?

Mmm.. that's not simple! (and it's the reason why I didn't file a
proper bug report).

At least I need some time to review carefully the GSL test code and
extract the "offending" lines...

Thanks for the quick response, though. When I have good news - if any
- I will write again.

Best,
Guido

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
MinGW-users mailing list
[hidden email]

You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users

_______________________________________________
This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.

Most annoying abuses are:
1) Top posting
2) HTML/MIME encoded mail
3) Improper quoting
4) Improper trimming
Reply | Threaded
Open this post in threaded view
|

Re: mingw+gsl: bug and workaround

Danny Smith

> > Can you reduce this to a minimal, standalone testcase?
>
> Mmm.. that's not simple! (and it's the reason why I didn't file a
> roper bug report).
>

Just add -save-temps to the CFLAGS for the testcase that fails and submit the .i and .s
files.


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
MinGW-users mailing list
[hidden email]

You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users

_______________________________________________
This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.

Most annoying abuses are:
1) Top posting
2) HTML/MIME encoded mail
3) Improper quoting
4) Improper trimming
Reply | Threaded
Open this post in threaded view
|

Re: mingw+gsl: bug and workaround

Guido De Rosa
2009/1/25 Danny Smith <[hidden email]>:

> Just add -save-temps to the CFLAGS for the testcase that fails and submit the .i and .s
> files.

Ok.

https://sourceforge.net/tracker2/?func=detail&aid=2535618&group_id=2435&atid=102435

Sorry, the amout of attached files is not minimal, but they are all
required to build test.exe, and they all produce different results
when compiled with --lots-of-equivalent-flags instead of -O2 .

Guido

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
MinGW-users mailing list
[hidden email]

You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users

_______________________________________________
This list observes the Etiquette found at
http://www.mingw.org/Mailing_Lists.
We ask that you be polite and do the same.

Most annoying abuses are:
1) Top posting
2) HTML/MIME encoded mail
3) Improper quoting
4) Improper trimming