public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: "Kaveh R. GHAZI" <ghazi@caip.rutgers.edu>
Cc: GCC <gcc@gcc.gnu.org>
Subject: Re: Using MPC Library with GCC
Date: Tue, 05 May 2009 17:04:00 -0000	[thread overview]
Message-ID: <4A00718E.50104@codesourcery.com> (raw)
In-Reply-To: <Pine.GSO.4.58.0905051107350.9541@caipclassic.rutgers.edu>

Kaveh R. GHAZI wrote:

> I didn't hear back from anyone opposing (or supporting!) MPC.  Does that
> mean it's no longer controversial?  Hopefully I've addressed the
> outstanding issues raised.
> 
> http://gcc.gnu.org/ml/gcc/2009-04/msg00741.html

I personally think relying on MPC is a reasonable choice, given the fact
that (as you say) the language specifications do in some cases require
support for these kinds of manipulations of complex numbers at compile-time.

In the past, however, other people have had objections.  I'd like to
give them more time (let's say one more week) to comment.  If that week
passes without negative comment, let's start coordinating how to move
forward with it.

Thanks,

-- 
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713

  reply	other threads:[~2009-05-05 17:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-27 18:54 Mark Mitchell
2009-04-28 18:13 ` Kaveh R. Ghazi
2009-05-05 15:15   ` Kaveh R. GHAZI
2009-05-05 17:04     ` Mark Mitchell [this message]
2009-05-13  8:41       ` Kaveh R. GHAZI
2009-05-13 11:51         ` Dave Korn
2009-05-13 15:42         ` Mark Mitchell
2009-05-30 18:07           ` Kaveh R. GHAZI
     [not found]             ` <4A28B124.50201@archlinux.org>
2009-06-05  5:46               ` Allan McRae
     [not found]             ` <BAY102-DAV10E7F9FA21B920680D391986480@phx.gbl>
2009-06-08  6:25               ` Kaveh R. Ghazi
2009-05-13 10:12 FX

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=4A00718E.50104@codesourcery.com \
    --to=mark@codesourcery.com \
    --cc=gcc@gcc.gnu.org \
    --cc=ghazi@caip.rutgers.edu \
    /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).