public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Pete Gontier <kokorozashi@gontier.org>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/8243: GCC 3.2 does not check for CMOV instruction before generating code
Date: Thu, 13 Feb 2003 19:56:00 -0000	[thread overview]
Message-ID: <20030213195601.791.qmail@sources.redhat.com> (raw)

The following reply was made to PR target/8243; it has been noted by GNATS.

From: Pete Gontier <kokorozashi@gontier.org>
To: <gcc-gnats@gcc.gnu.org>,
	<forsmark@odense.kollegienet.dk	<gcc-bugs@gcc.gnu.org	<nobody@gcc.gnu.org	<gcc-prs@gcc.gnu.orgCc:  
Subject: Re: target/8243: GCC 3.2 does not check for CMOV instruction
	before generating code
Date: Thu, 13 Feb 2003 11:54:39 -0800

 I don't think I fully understand the closure of this bug. I understand if by
 i686 you really mean Pentium Pro. (I hope that's documented.) The claim that
 it would be dumb for GCC to generate code which checks for CMOV before using
 it also makes sense. However, if there were a way to tell GCC not to
 generate CMOV instructions in the first place, that would seem reasonable,
 too, assuming there are other i686 optimizations worth doing.
 


             reply	other threads:[~2003-02-13 19:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-13 19:56 Pete Gontier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-13 20:36 Pete Gontier
2002-10-21 23:55 rth
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=20030213195601.791.qmail@sources.redhat.com \
    --to=kokorozashi@gontier.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).