From: Ian Lance Taylor <iant@google.com>
To: "Christian Grössler" <chris@groessler.org>
Cc: gcc@gcc.gnu.org
Subject: Re: Problem updating 2yr old port
Date: Mon, 27 Dec 2010 23:22:00 -0000 [thread overview]
Message-ID: <mcr62uevm1z.fsf@google.com> (raw)
In-Reply-To: <4D18FDDF.5070703@groessler.org> ("Christian =?utf-8?Q?Gr?= =?utf-8?Q?=C3=B6ssler=22's?= message of "Mon, 27 Dec 2010 21:58:07 +0100")
Christian Grössler <chris@groessler.org> writes:
> Looking at the history of optabs.c, the MODE_CC test was introduced when merging the cond-optab branch
> to main. I didn't find a description of the cond-optab branch and what it was supposed to do.
This is the description of the now-merged cond-optab branch, from
http://gcc.gnu.org/ml/gcc/2009-04/msg00211.html :
This branch is to clean up and simplify the implementation of
conditional operations (branches, stores, moves, etc.) in expand and
in the machine descriptions. Patches should be marked with the tag
[cond-optab] in the subject line. The branch is maintained by Paolo
Bonzini. Pending further testing, the branch is ready to be merged
into mainline and only bug and documentation fixes should be
committed.
As I recall the basic idea was to generate all conditional branches via
the cbranchMODE4 pattern rather than using separate compare and branch
patterns.
I couldn't figure out which assertion you hit so I'm not sure what else
to say. A const_int is always VOIDmode, and there should be no problem
comparing a value to a const_int.
Ian
next prev parent reply other threads:[~2010-12-27 23:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-27 20:58 Christian Grössler
2010-12-27 23:22 ` Ian Lance Taylor [this message]
2010-12-28 1:03 ` Christian Grössler
2010-12-28 5:37 ` Ian Lance Taylor
2010-12-29 20:53 ` Christian Grössler
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=mcr62uevm1z.fsf@google.com \
--to=iant@google.com \
--cc=chris@groessler.org \
--cc=gcc@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).