public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: aoliva@gcc.gnu.org
To: alatham@flexsys-group.com, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: c/3376: optimised code wrong in simple for statement
Date: Sat, 23 Jun 2001 00:04:00 -0000	[thread overview]
Message-ID: <20010623070412.18413.qmail@sourceware.cygnus.com> (raw)

Synopsis: optimised code wrong in simple for statement

State-Changed-From-To: open->closed
State-Changed-By: aoliva
State-Changed-When: Sat Jun 23 00:04:12 2001
State-Changed-Why:
    It seems that you forgot to attach the short test program.
    
    Anyway, 2.96 is not a version of GCC released by the FSF.  To report bugs in the Red Hat version of GCC, use the Red Hat bug reporting program at bugzilla.redhat.com.  But make sure you get the latest update of the GCC RPMs first.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3376&database=gcc


             reply	other threads:[~2001-06-23  0:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-23  0:04 aoliva [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-22 10:56 alatham

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=20010623070412.18413.qmail@sourceware.cygnus.com \
    --to=aoliva@gcc.gnu.org \
    --cc=alatham@flexsys-group.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --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).