public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ben Elliston <bje@au1.ibm.com>
To: Danny Smith <dannysmith@clear.net.nz>
Cc: GCC-patches <gcc-patches@gcc.gnu.org>
Subject: Re: RFA: Enable DFP/BID on  i?86-pc-mingw32 target
Date: Sat, 21 Jul 2007 19:56:00 -0000	[thread overview]
Message-ID: <1185040836.9678.2.camel@localhost> (raw)
In-Reply-To: <000001c7cb79$8e6b0c50$184861cb@THOMAS>

On Sat, 2007-07-21 at 21:28 +1200, Danny Smith wrote:

> Is this OK for mainline? 

This patch doesn't really cover my maintenance area (it's just
configury), but I wanted to throw a point in: I assume that MinGW
conforms to the MS ABI?  If so, you're making an ABI extension here
because of the way that the x86 backend passes decimal float parameters,
etc.

Do you intend to just make that an undocumented extension for the time
being?  What if you wish to later conform to the MS ABI?  You'll break
your current ABI.

Cheers, Ben


  parent reply	other threads:[~2007-07-21 18:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-21 10:15 Danny Smith
2007-07-21 10:57 ` Paolo Bonzini
2007-07-21 19:56 ` Ben Elliston [this message]
2007-07-22 10:23   ` Danny Smith

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=1185040836.9678.2.camel@localhost \
    --to=bje@au1.ibm.com \
    --cc=dannysmith@clear.net.nz \
    --cc=gcc-patches@gcc.gnu.org \
    /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).