On Mon, Oct 6, 2008 at 4:36 PM, Ben Elliston <[EMAIL PROTECTED]> wrote:
> On Mon, 2008-10-06 at 16:10 -0700, Kaveh R. Ghazi wrote:
>
>> The last time this came up, the consensus was that we should not hard fail
>> the configure script even if the user would then be missing some mpfr bugfix
>> in the latest/greatest release. That's why we have the minimum/recommended
>> split.
>
> Doesn't this mean that we can then have two different versions of GCC
> (as identified by gcc --version), linked with different mpfr libraries,
> that may exhibit different behaviour?
Semi, we do output the version of MPFR in cc1 --version output:
GNU C (GCC) version 4.4.0 20081003 (experimental) [trunk revision
140850] (i386-apple-darwin8.11.1)
compiled by GNU C version 4.4.0 20081003 (experimental) [trunk
revision 140850], GMP version 4.2.2, MPFR version 2.3.0.
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
Thanks,
Andrew Pinski
