This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: configuring in-tree gmp/mpfr with "none"?

From: Paolo Bonzini <bonzini at gnu dot org>
To: Jay <jayk123 at hotmail dot com>
Cc: Andrew Pinski <pinskia at gmail dot com>, gcc at gcc dot gnu dot org
Date: Mon, 04 Aug 2008 13:05:09 +0200
Subject: Re: configuring in-tree gmp/mpfr with "none"?
References: <BAY139-W162C29DAF463FFF6ABB94FE6AE0@phx.gbl> <de8d50360806171039g13d89b36necbc8a67b853e278@mail.gmail.com> <BAY139-W155015ADB5180EDEAB8B9CE6AB0@phx.gbl> <de8d50360806180353x64578a63y20508f5841efd1f@mail.gmail.com> <COL101-W53CA343E1A70D50CEF70C1E67C0@phx.gbl> <4891C3E7.4050401@gnu.org> <COL101-W39765618E56F15427E078FE6780@phx.gbl>

Jay wrote:

Because at some point, no released version worked on intel macs.
Long since passed and can be removed?

I don't think so, http://gmp.darwinports.com/ shows that it is still a problem with 4.2.2. Besides, GMP's authors say that it is often a stress test for compilers, so using more C and less assembly can be a good thing (GCC's usage of GMP does not include manipulating really really huge numbers).

gmp/configure is where the blame really lies, but if gcc configured gmp "normally",
this wouldn't occur. Or, is cpu=none not so abnormal? Just that I hadn't seen it?

It's a GMP-only thing.

Given that this is a problem because of Python's apparently broken handling of signals, we cannot do anything about it. Complain with the Python maintainers that they should reset the signals they ignore, before exec-ing another program.

Paolo

Follow-Ups:
- Re: configuring in-tree gmp/mpfr with "none"?
  - From: Vincent Lefevre

References:
- RE: configuring in-tree gmp/mpfr with "none"?
  - From: Jay

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]