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/7265: [ia64] HP-UX cross Linux compiler cannot build libgcc
Date: Wed, 07 May 2003 18:56:00 -0000	[thread overview]
Message-ID: <20030507185601.657.qmail@sources.redhat.com> (raw)

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

From: Dara Hazeghi <dhazeghi@yahoo.com>
To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org,
   jnaset@rsn.hp.com
Cc:  
Subject: Re: target/7265: [ia64] HP-UX cross Linux compiler cannot build libgcc
Date: Wed, 7 May 2003 11:52:21 -0700

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- 
 trail&database=gcc&pr=7265
 
 Hello,
 
 I am unable to duplicate the submitter's error with the test sample.  
 The .i file has errors in it and will not compile with gcc 3.1, 3.2.3,  
 or 3.3 branch. The shorter testcase compiles with 3.1, 3.2.3, 3.3  
 branch, and mainline. Could the submitter please verify whether this  
 error occurs in newer releases of gcc, and if so possibly submit an  
 updated version of the preprocessed source? Thanks,
 
 Dara
 


             reply	other threads:[~2003-05-07 18:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-07 18:56 Dara Hazeghi [this message]
2003-05-07 21:12 bangerth

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