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: middle-end/3805: [AVR] Chokes on while building C code for AVR microcontrollers
Date: Fri, 09 May 2003 07:46:00 -0000	[thread overview]
Message-ID: <20030509074600.27951.qmail@sources.redhat.com> (raw)

The following reply was made to PR middle-end/3805; it has been noted by GNATS.

From: Dara Hazeghi <dhazeghi@yahoo.com>
To: gcc-gnats@gcc.gnu.org, mikep@core.ucsd.edu
Cc:  
Subject: Re: middle-end/3805: [AVR] Chokes on while building C code for AVR microcontrollers
Date: Fri, 9 May 2003 00:40:32 -0700

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- 
 trail&database=gcc&pr=3805
 
 Hello,
 
 could the submitter please verify whether this bug remains in more  
 current versions of gcc (ie 3.2.3). I cannot replicate this error with  
 3.1, 3.3 branch or mainline. Thanks,
 
 Dara
 


             reply	other threads:[~2003-05-09  7:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-09  7:46 Dara Hazeghi [this message]
2003-05-09  8:46 Michael Przybylski
2003-05-09  9:16 Dara Hazeghi
2003-05-09 15:22 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=20030509074600.27951.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).