From: Ian Lance Taylor <iant@google.com>
To: Rajiv KI <rajivkumarsingla@gmx.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: mode of CONST_INT
Date: Tue, 23 Mar 2010 03:27:00 -0000 [thread overview]
Message-ID: <mcr8w9j3ell.fsf@dhcp-172-17-9-151.mtv.corp.google.com> (raw)
In-Reply-To: <27982352.post@talk.nabble.com> (Rajiv KI's message of "Sun\, 21 Mar 2010 21\:38\:15 -0700 \(PDT\)")
Rajiv KI <rajivkumarsingla@gmx.com> writes:
> Ian Lance Taylor-3 wrote:
>>
>> By definition CONST_INT rtxes have no mode. They take on whatever
>> mode the context requires. This is indeed awkward in some cases, and
>> sometimes requires maintaining the mode separately.
>>
>> Ian
>>
>>
>
> Ya its really not fine that it takes whatever mode.
>
> Please tell is there any way in gcc by which i can separately maintain mode
> of 'CONST_INT' RTX.
You have to provide a mode for any case where you might see a
CONST_INT. The gcc middle-end and backends already does this, because
they must.
Ian
prev parent reply other threads:[~2010-03-23 3:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 13:29 Rajiv KI
2010-03-19 15:50 ` Ian Lance Taylor
2010-03-22 8:06 ` Rajiv KI
2010-03-23 3:27 ` Ian Lance Taylor [this message]
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=mcr8w9j3ell.fsf@dhcp-172-17-9-151.mtv.corp.google.com \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=rajivkumarsingla@gmx.com \
/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).