From: David Edelsohn <dje.gcc@gmail.com>
To: Mike Stump <mikestump@comcast.net>,
Kenneth Zadeck <zadeck@naturalbridge.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: wide-int, rs6000
Date: Mon, 25 Nov 2013 23:07:00 -0000 [thread overview]
Message-ID: <CAGWvny=BikM8xtDoRbKqL3sQQt+4-h2ZbL_F0zv+ZJmbAXOs9A@mail.gmail.com> (raw)
In-Reply-To: <42DC4C50-3430-4A2E-914C-FEC7A0DB7DEB@comcast.net>
Thanks for doing this conversion work. A few questions and comments:
1) Because rs6000 is one of the few ports that was completely
converted to wide-int instead of simply accommodating wide-int, what
is the compile-time performance impact of this conversion?
2) non_logical_cint_operand changed const_double to const_wide_int, it
did not add the additional CODE. Mike explained why in a private
conversation, but the ChangeLog should be corrected.
3) altivec_resolve_overloaded_builtin, both hunks should be converted
the same way, using tree_fits_uhwi_p
- && TREE_CODE (arg2) == INTEGER_CST
- && TREE_INT_CST_HIGH (arg2) == 0
- && (TREE_INT_CST_LOW (arg2) == 0 || TREE_INT_CST_LOW (arg2) == 1))
+ && tree_fits_uhwi_p (arg2)
+ && wi::ltu_p (arg2, 2))
4) easy_altivec_constant, the comment about 32 bit should be removed
because wide-int should remove the dependency on 32 bit vs 64 bit host
wide int.
5) rs6000_aggregate_candidate, is this change correct for Ada and
non-constant type size?
The rest looks good. I'd like to see the revised patch before approving.
Thanks, David
On Sat, Nov 23, 2013 at 2:22 PM, Mike Stump <mikestump@comcast.net> wrote:
> Richi has asked the we break the wide-int patch so that the individual port and front end maintainers can review their parts without have to go through the entire patch. This patch covers the rs6000 port.
>
> Ok?
>
next prev parent reply other threads:[~2013-11-25 20:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-23 22:37 Mike Stump
2013-11-25 23:07 ` David Edelsohn [this message]
2013-11-26 7:54 ` Mike Stump
2013-11-26 7:56 ` Mike Stump
2013-11-26 14:51 ` Richard Sandiford
2013-11-27 3:45 ` Mike Stump
2013-11-27 2:27 ` Mike Stump
2013-11-27 2:34 ` Mike Stump
2013-11-27 5:34 ` Mike Stump
2013-11-27 6:45 ` David Edelsohn
2013-11-27 7:22 ` Kenneth Zadeck
2013-11-27 12:35 ` Richard Biener
2014-06-28 10:31 ` [commit] Fix ABI fallout (Re: wide-int, rs6000) Ulrich Weigand
2014-06-28 19:18 ` Mike Stump
2014-06-30 11:02 ` Ulrich Weigand
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='CAGWvny=BikM8xtDoRbKqL3sQQt+4-h2ZbL_F0zv+ZJmbAXOs9A@mail.gmail.com' \
--to=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikestump@comcast.net \
--cc=zadeck@naturalbridge.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).