From: Richard Sandiford <rdsandiford@googlemail.com>
To: gcc-patches@gcc.gnu.org
Subject: [0/4] Make more use of tree_to_[su]hwi
Date: Tue, 19 Nov 2013 12:35:00 -0000 [thread overview]
Message-ID: <871u2cpq4u.fsf@talisman.default> (raw)
Dull series, sorry, but this is another change taken from wide-int.
After checking host_integerp (now tree_fits_[su]hwi_p), the preferred way
of getting the HWI seemed to be tree_low_cst (now tree_to_[su]hwi).
This series mops up some cases where TREE_INT_CST_LOW was used directly.
Tested on x86_64-linux-gnu.
Thanks,
Richard
next reply other threads:[~2013-11-19 11:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 12:35 Richard Sandiford [this message]
2013-11-19 12:42 ` [1/4] Use tree_to_uhwi with an inlined tree_fits_uhwi_p test Richard Sandiford
2013-11-20 10:56 ` Richard Biener
2013-11-19 12:51 ` [2/4] Use tree_to_uhwi when folding (x >> c) << c Richard Sandiford
2013-11-19 20:49 ` Jeff Law
2013-11-19 13:32 ` [3/4] Avoid undefined operation in overflow check Richard Sandiford
2013-11-20 11:26 ` Richard Biener
2013-11-19 13:38 ` [4/4] The rest of the tree_to_[su]hwi changes Richard Sandiford
2013-11-20 11:27 ` Richard Biener
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=871u2cpq4u.fsf@talisman.default \
--to=rdsandiford@googlemail.com \
--cc=gcc-patches@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).