--- Comment #3 from mikpe at it dot uu dot se 2009-12-09 16:07 ---
(In reply to comment #2)
libmpfr must be a shared object because libmpc relies on hidden, global state
in libmpfr. If libmpfr is linked statically with libmpc and with GCC, each
receives different instances of the
--- Comment #4 from dje at gcc dot gnu dot org 2009-12-09 16:36 ---
I think the problem is bad design of MPFR, not a bug in MPC. GCC uses
mpfr_clear_flags(), mpfr_overflow_p() and mpfr_underflow_p() for results of
computations in both MPFR and MPC, which uses MPFR. These rely on the
--- Comment #2 from dje at gcc dot gnu dot org 2009-12-09 00:03 ---
libmpfr must be a shared object because libmpc relies on hidden, global state
in libmpfr. If libmpfr is linked statically with libmpc and with GCC, each
receives different instances of the global variables.
--
dje
--- Comment #1 from dje at gcc dot gnu dot org 2009-08-12 17:35 ---
This started failing after I started compiling with MPC library. Is this an
MPC bug or interaction bug?
--
dje at gcc dot gnu dot org changed:
What|Removed |Added
