public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/10181: [x86] wrong conversion [unsigned -> double] with [-masm=intel]
Date: Mon, 12 May 2003 00:36:00 -0000	[thread overview]
Message-ID: <20030512003600.18976.qmail@sources.redhat.com> (raw)

The following reply was made to PR target/10181; it has been noted by GNATS.

From: Dara Hazeghi <dhazeghi@yahoo.com>
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: target/10181: [x86] wrong conversion [unsigned -> double] with [-masm=intel]
Date: Sun, 11 May 2003 17:33:09 -0700 (PDT)

 --- Markus Mauhart <mmauhart@chello.at> wrote:
 > >
 >
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-
 > 
 > > trail&database=gcc&pr=10181
 > > 
 > > Hello,
 > > 
 > > could you please verify that this error is still
 > present in a more  
 > > current gcc release (ie 3.2.3)? With gcc 3.2.3,
 > 3.3 branch and mainline  
 > > on i686-linux, the testcase works fine (ie
 > conversions are all  
 > > correct). Thanks,
 > > 
 > > Dara
 > 
 > Unfortunately I cannot test newer GCC versions, mine
 > is
 > "gcc version 3.2 20020927 (prerelease)" from the
 > current Cygwin,
 > and AFAIK it will take some months until there comes
 > a newer
 > 'official' version.
 > Additionally I feel not fit enough for trying to do
 > my private
 > build of newer GCC sources under cygwin.
 > OTOH what you tell about "gcc 3.2.3, 3.3 branch and
 > mainline  
 > on i686-linux" sounds IMHO good enough to close the
 > report.
 
 Okay. I guess we can close it for now then, but if 3.3
 has it, a new bug can be opened.
 
 Dara
 
 __________________________________
 Do you Yahoo!?
 The New Yahoo! Search - Faster. Easier. Bingo.
 http://search.yahoo.com


             reply	other threads:[~2003-05-12  0:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-12  0:36 Dara Hazeghi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-12 10:30 steven
2003-05-10 20:46 Dara Hazeghi

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=20030512003600.18976.qmail@sources.redhat.com \
    --to=dhazeghi@yahoo.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).