From: Mike Stump <mikestump@comcast.net>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Richard Henderson <rth@redhat.com>,
gcc-patches@gcc.gnu.org, David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [PATCH 06/15] rs6000: Use rldiwi in constant construction
Date: Thu, 13 Aug 2015 19:01:00 -0000 [thread overview]
Message-ID: <CE501431-5F6E-42C8-B859-1FB953A486D3@comcast.net> (raw)
In-Reply-To: <20150813024346.GB19357@gate.crashing.org>
On Aug 12, 2015, at 7:43 PM, Segher Boessenkool <segher@kernel.crashing.org> wrote:
> Yes. And there are much worse problems, like many things not working
> right if your HOST_WIDE_INT would happen to be more than 64 bits; we
> cannot really shake those out because there is no actual system to
> test that on -- but it also doesn't actually matter, because there is
> no system to run it on :-)
Lots of systems support 128 bit types just fine, and one could use TImode for HOST_WIDE_INT, if one really, really wanted to. x86_64 I think is one of those systems.
next prev parent reply other threads:[~2015-08-13 19:00 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 1:11 [PATCH ppc64,aarch64,alpha 00/15] Improve backend constant generation Richard Henderson
2015-08-12 1:11 ` [PATCH 01/15] rs6000: Split out rs6000_is_valid_and_mask_wide Richard Henderson
2015-08-12 13:24 ` Segher Boessenkool
2015-08-12 15:50 ` Richard Henderson
2015-08-13 2:29 ` Segher Boessenkool
2015-08-12 1:11 ` [PATCH 05/15] rs6000: Move constant via mask into build_set_const_data Richard Henderson
2015-08-12 1:12 ` [PATCH 12/15] aarch64: Test for duplicated 32-bit halves Richard Henderson
2015-08-12 1:12 ` [PATCH 13/15] alpha: Use hashing infrastructure for generating constants Richard Henderson
2015-08-12 1:12 ` [PATCH 15/15] alpha: Remove alpha_emit_set_long_const Richard Henderson
2015-08-12 1:12 ` [PATCH 02/15] rs6000: Make num_insns_constant_wide static Richard Henderson
2015-08-12 1:12 ` [PATCH 04/15] rs6000: Implement set_const_data infrastructure Richard Henderson
2015-08-12 13:53 ` Segher Boessenkool
2015-08-12 1:12 ` [PATCH 09/15] rs6000: Use xoris in constant construction Richard Henderson
2015-08-12 1:12 ` [PATCH 03/15] rs6000: Tidy num_insns_constant vs CONST_DOUBLE Richard Henderson
2015-08-12 1:12 ` [PATCH 11/15] aarch64: Use hashing infrastructure for generating constants Richard Henderson
2015-08-12 1:12 ` [PATCH 06/15] rs6000: Use rldiwi in constant construction Richard Henderson
2015-08-12 14:02 ` Segher Boessenkool
2015-08-12 15:55 ` Richard Henderson
2015-08-13 2:43 ` Segher Boessenkool
2015-08-13 19:01 ` Mike Stump [this message]
2015-08-13 20:30 ` Joseph Myers
2015-08-12 1:12 ` [PATCH 08/15] rs6000: Generalize masking in constant generation Richard Henderson
2015-08-12 1:12 ` [PATCH 10/15] rs6000: Use rotldi " Richard Henderson
2015-08-12 1:12 ` [PATCH 07/15] rs6000: Generalize left shift " Richard Henderson
2015-08-12 1:12 ` [PATCH 14/15] alpha: Split out alpha_cost_set_const Richard Henderson
2015-08-12 8:32 ` [PATCH ppc64,aarch64,alpha 00/15] Improve backend constant generation Segher Boessenkool
2015-08-12 15:32 ` Richard Henderson
2015-08-13 3:07 ` Segher Boessenkool
2015-08-13 5:36 ` Segher Boessenkool
2015-08-13 3:10 ` Segher Boessenkool
2015-08-13 11:32 ` David Edelsohn
2015-08-12 8:32 ` Richard Earnshaw
2015-08-12 8:43 ` Richard Earnshaw
2015-08-12 9:02 ` Richard Earnshaw
2015-08-12 15:45 ` Richard Henderson
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=CE501431-5F6E-42C8-B859-1FB953A486D3@comcast.net \
--to=mikestump@comcast.net \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rth@redhat.com \
--cc=segher@kernel.crashing.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).