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/7285: [ia64] unsigned-to-floating conversion not spec conformant
Date: Sat, 17 May 2003 10:06:00 -0000	[thread overview]
Message-ID: <20030517100601.30831.qmail@sources.redhat.com> (raw)

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

From: Dara Hazeghi <dhazeghi@yahoo.com>
To: jbeulich@novell.com, gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org
Cc:  
Subject: Re: target/7285: [ia64] unsigned-to-floating conversion not spec conformant
Date: Sat, 17 May 2003 02:56:32 -0700

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- 
 trail&database=gcc&pr=7285
 
 Hello,
 
 there's been a fair bit of changes dealing with ia64 since gcc 3.1.  
 Would it be possible for you to check whether this problem is still  
 present on gcc 3.3? Thanks,
 
 Dara
 


             reply	other threads:[~2003-05-17 10:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-17 10:06 Dara Hazeghi [this message]
2003-05-21  9:34 ehrhardt

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=20030517100601.30831.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).