public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: hp@gcc.gnu.org
To: adam@yggdrasil.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: optimization/7001: gcc-3.1 and 3.04 on x86 generate bad memset code
Date: Wed, 12 Jun 2002 19:21:00 -0000	[thread overview]
Message-ID: <20020613022118.21750.qmail@sources.redhat.com> (raw)

Synopsis: gcc-3.1 and 3.04 on x86 generate bad memset code

State-Changed-From-To: open->closed
State-Changed-By: hp
State-Changed-When: Wed Jun 12 19:21:17 2002
State-Changed-Why:
    Submitter reports that this is a duplicate of PR 6703,
    confirms that the patch in 6703 solved this problem.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7001


             reply	other threads:[~2002-06-13  2:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-12 19:21 hp [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-12 16:16 Adam J. Richter
2002-06-12  9:56 Glen Nakamura
2002-06-12  0:36 adam

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=20020613022118.21750.qmail@sources.redhat.com \
    --to=hp@gcc.gnu.org \
    --cc=adam@yggdrasil.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@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).