public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: FX Coudert <fxcoudert@gmail.com>
To: Paul Thomas <paulthomas2@wanadoo.fr>
Cc: GFORTRAN list <fortran@gcc.gnu.org>,
	 GCC-patches list <gcc-patches@gcc.gnu.org>
Subject: Re: [gfortran,patch] Fix code generated for NINT
Date: Tue, 31 Jul 2007 23:24:00 -0000	[thread overview]
Message-ID: <9F375F17-8945-4529-AB63-D9156DA056AC@gmail.com> (raw)
In-Reply-To: <46AFABE4.2010707@wanadoo.fr>

> Does Cygwin comply? I am just about to launch a regtest.  I am only  
> asking because the consequences of the NINT bug are particularly  
> dire. :-)

Yes, I know. I have lots of code myself which will probably get a  
large hit in performance due to that patch, and I was really  
reluctant to do it for such a simple case, but I can't find another  
way of fixing it :(

Oh, and by the way, a cygwin test can only help, though I think it  
has lround.

FX

      reply	other threads:[~2007-07-31 21:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-31 21:39 FX Coudert
2007-07-31 21:56 ` Paul Thomas
2007-07-31 23:24   ` FX Coudert [this message]

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=9F375F17-8945-4529-AB63-D9156DA056AC@gmail.com \
    --to=fxcoudert@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=paulthomas2@wanadoo.fr \
    /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).