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/9883: [mipsel] segfault while compiling libgcc2.c
Date: Fri, 09 May 2003 08:56:00 -0000	[thread overview]
Message-ID: <20030509085600.6842.qmail@sources.redhat.com> (raw)

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

From: Dara Hazeghi <dhazeghi@yahoo.com>
To: gcc-gnats@gcc.gnu.org, sherw@mail.com
Cc:  
Subject: Re: bootstrap/9883: [mipsel] segfault while compiling libgcc2.c
Date: Fri, 9 May 2003 01:46:32 -0700

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- 
 trail&database=gcc&pr=9883
 
 Hello,
 
 can the submitter confirm that this bug still occurs? I cannot  
 reproduce it with mipsel cross compilers of 3.2, 3.3 branch and  
 mainline (20030506) versions of gcc.
 
 Thanks,
 
 Dara
 


             reply	other threads:[~2003-05-09  8:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-09  8:56 Dara Hazeghi [this message]
2003-05-09 15:24 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=20030509085600.6842.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).