public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Steven Bosscher <s.bosscher@student.tudelft.nl> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/8634: [3.2/3.3/3.4 regression] incorrect code for inlining of memcpy under -O2 Date: Sun, 06 Apr 2003 15:36:00 -0000 [thread overview] Message-ID: <20030406153600.13937.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/8634; it has been noted by GNATS. From: Steven Bosscher <s.bosscher@student.tudelft.nl> To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, duchier@ps.uni-sb.de, gcc-prs@gcc.gnu.org, mark@codesourcery.com Cc: Subject: Re: optimization/8634: [3.2/3.3/3.4 regression] incorrect code for inlining of memcpy under -O2 Date: Sun, 06 Apr 2003 17:29:20 +0200 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8634 Thanks to Sherlock Hubicka, this patch by Zdenek has re-surfaced: http://gcc.gnu.org/ml/gcc-patches/2003-02/msg01655.html The message was probably ignored because of the inspired subject line: "[PATCH] ..." (sic). Greetz Steven
next reply other threads:[~2003-04-06 15:36 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-06 15:36 Steven Bosscher [this message] 2003-04-07 23:00 rth
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=20030406153600.13937.qmail@sources.redhat.com \ --to=s.bosscher@student.tudelft.nl \ --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: linkBe 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).