public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <bonzini@gnu.org>
To: Jay <jayk123@hotmail.com>
Cc: Andrew Pinski <pinskia@gmail.com>, gcc@gcc.gnu.org
Subject: Re: configuring in-tree gmp/mpfr with "none"?
Date: Mon, 04 Aug 2008 11:06:00 -0000	[thread overview]
Message-ID: <4896E265.4020800@gnu.org> (raw)
In-Reply-To: <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

  reply	other threads:[~2008-08-04 11:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-15 16:50 Jay
2008-06-17 17:40 ` Andrew Pinski
2008-06-18  4:54   ` Jay
     [not found]   ` <BAY139-W155015ADB5180EDEAB8B9CE6AB0@phx.gbl>
2008-06-18 10:54     ` Andrew Pinski
2008-07-31 11:45       ` Jay
2008-07-31 15:00         ` Paolo Bonzini
2008-08-04 10:26           ` Jay
2008-08-04 11:06             ` Paolo Bonzini [this message]
2008-08-04 14:47               ` Vincent Lefevre

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4896E265.4020800@gnu.org \
    --to=bonzini@gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=jayk123@hotmail.com \
    --cc=pinskia@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).