[PATCH]: PR29335 evaluate transcendentals at compile-time using MPFR [take 3]

Kaveh R. GHAZI ghazi@caip.rutgers.edu
Sun Oct 22 07:42:00 GMT 2006


On Sat, 21 Oct 2006, Mark Mitchell wrote:

> Kaveh R. GHAZI wrote:
> > On Fri, 20 Oct 2006, Joseph S. Myers wrote:
> >
> >> My view is: put in the installation documentation the requirement for at
> >> least cumulative patch version n.  Put a testcase in the GCC testsuite
> >> that shows if your MPFR is too old.
> >>
> >> Then, if there is no new MPFR release for which configure checks can be
> >> made by the time 4.3 branches, consider workarounds.
> >
> > Sounds fine, agreed.
>
> That sounds good to me as well.  I do not think that we need to do
> anything at configure-time, so long as we document the patch in our
> installation requirements.  That's not to say detecting the problem at
> configure-time isn't a good thing, but I don't think it's a necessary thing.
> Mark Mitchell

Okay, was your reply meant as a general agreement on the approach to MPFR
version detection, or a specific approval for the middle-end patch which
uses MPFR to evaluate sin, etc. ?

		Thanks,
		--Kaveh
--
Kaveh R. Ghazi			ghazi@caip.rutgers.edu



More information about the Gcc-patches mailing list