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/6115: [alpha-osf]mips-tfile errors out, dependent on filename order in command
Date: Sat, 17 May 2003 09:46:00 -0000	[thread overview]
Message-ID: <20030517094602.23233.qmail@sources.redhat.com> (raw)

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

From: Dara Hazeghi <dhazeghi@yahoo.com>
To: tilps@hotmail.com, gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org
Cc:  
Subject: Re: target/6115: [alpha-osf]mips-tfile errors out, dependent on filename order in command
Date: Sat, 17 May 2003 02:42:35 -0700

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- 
 trail&database=gcc&pr=6115
 
 Hello,
 
 there have been a lot of changes between gcc 3.2 and 3.3. Would it be  
 possible to check whether this problem still occurs with gcc 3.3?  
 Thanks,
 
 Dara
 


             reply	other threads:[~2003-05-17  9:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-17  9:46 Dara Hazeghi [this message]
2003-05-21  9:45 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=20030517094602.23233.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).