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: bootstrap/6972: libgcc2.c GCC 3.1 Cross-compiler Compilation Errors
Date: Thu, 08 May 2003 03:56:00 -0000	[thread overview]
Message-ID: <20030508035600.31081.qmail@sources.redhat.com> (raw)

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

From: Dara Hazeghi <dhazeghi@yahoo.com>
To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, jona_hugh_rob@yahoo.co.uk
Cc:  
Subject: Re: bootstrap/6972: libgcc2.c GCC 3.1 Cross-compiler Compilation Errors
Date: Wed, 7 May 2003 20:55:03 -0700

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- 
 trail&database=gcc&pr=6972
 
 Hello,
 
 could the submitter of this report please include the preprocessed  
 source which is crashing, and perhaps test a more current version of  
 gcc? I am able to build arm-elf crosses from 3.1, 3.3 branch and  
 mainline, none of which fail at the spot specified, and without a  
 testcase, it;s difficult to test if the particular bug encountered  
 still exists. Thanks,
 
 Dara
 


             reply	other threads:[~2003-05-08  3:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-08  3:56 Dara Hazeghi [this message]
2003-05-14 10:55 giovannibajo

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