Issues with mfpmath=both

[Zbigniew Luszpinski]

> Hi,
> 
> correction: 4.4 lists it' just 4.2 not. So ppl upgrading from gcc below 
> 4.4 will have trouble to upgrade. And ppl below gcc 4.4 will have 
> trouble to compile anything IF they use "both".
> 
> <lazyape> wdp__, as far as concerne the mfpmath=both issue i have to say 
> that gcc-4.4.2 man page list the 'both' choice for the mfpmath option 
> but also informs that it is an experimental feature
>

I introduced 'both' parameter because some modules breaks because of comma between 387,sse.
But only for 4.4 plugin. The 4.2 and lower plugins are untouched because both parameter is not present there.
Do you have gcc 4.2 plugin set as default? Did you try to re set fpu parameter after switching default compiler to gcc 4.2?
It is possible you have found bug in Lunar's plugin management. It would be very bad thing if lunar update would set default gcc plugin to 4.4 if gcc 4.2 is still in use. If you confirm this bug I will look at it more closely and provide some kind of fix to keep gcc and plugin version bound together. You can now have other problems with features which came with gcc4.4 like phenom, autodetect, new Intel sse... not present in older gcc. Make sure in Lunar menu you have set as default the right plugin. Gcc plugin and gcc version must equal to match features they provide.

Experimental feature is to use sse and 387 together. Such warning is with every gcc release, I remember it since gcc3. The 'both' word is just rename of sse,387 to eliminate comma problem in some build scripts. I always used sse,387 and now both parameter. So far all modules work perfect.

have a nice day,
Zbigniew Luszpinski