public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rth@gcc.gnu.org To: dyatchkov@mcst.ru, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: optimization/8110: GCC 3.2: wrong code optimization with -O2 Date: Tue, 01 Oct 2002 14:19:00 -0000 [thread overview] Message-ID: <20021001211901.7905.qmail@sources.redhat.com> (raw) Synopsis: GCC 3.2: wrong code optimization with -O2 State-Changed-From-To: open->closed State-Changed-By: rth State-Changed-When: Tue Oct 1 14:19:00 2002 State-Changed-Why: The code in rtx_alloc is broken in spec2k. Use the following. --- rtl.c.orig Tue Oct 1 14:16:34 2002 +++ rtl.c Tue Oct 1 14:17:35 2002 @@ -234,9 +234,7 @@ one int, but we don't want to assume that and it isn't very portable anyway; this is. */ - length = (sizeof (struct rtx_def) - sizeof (rtunion) - 1) / sizeof (int); - for (; length >= 0; length--) - ((int *) rt)[length] = 0; + memset (rt, 0, sizeof (struct rtx_def) - sizeof (rtunion)); PUT_CODE (rt, code); http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8110
next reply other threads:[~2002-10-01 21:19 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-01 14:19 rth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-01 9:26 dyatchkov
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=20021001211901.7905.qmail@sources.redhat.com \ --to=rth@gcc.gnu.org \ --cc=dyatchkov@mcst.ru \ --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: 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).