public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rth@gcc.gnu.org To: forsmark@odense.kollegienet.dk, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: target/8243: GCC 3.2 does not check for CMOV instruction before generating code Date: Mon, 21 Oct 2002 23:55:00 -0000 [thread overview] Message-ID: <20021022065544.17560.qmail@sources.redhat.com> (raw) Synopsis: GCC 3.2 does not check for CMOV instruction before generating code State-Changed-From-To: open->closed State-Changed-By: rth State-Changed-When: Mon Oct 21 23:55:43 2002 State-Changed-Why: Defined as "not a bug". When we say i686, we really do mean "pentiumpro". Checking for cmov is a waste of time; it'd be faster to not use it than to check. Use -march=i586 instead. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8243
next reply other threads:[~2002-10-22 6:55 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-21 23:55 rth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-13 20:36 Pete Gontier 2003-02-13 19:56 Pete Gontier 2002-10-16 10:16 forsmark
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=20021022065544.17560.qmail@sources.redhat.com \ --to=rth@gcc.gnu.org \ --cc=forsmark@odense.kollegienet.dk \ --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).