From: Eric Botcazou <ebotcazou@adacore.com>
To: Richard Sandiford <richard.sandiford@arm.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [1/2] PR88598: Optimise x * { 0 or 1, 0 or 1, ... }
Date: Fri, 04 Jan 2019 12:25:00 -0000 [thread overview]
Message-ID: <1764423.ZT9OE2iC5R@polaris> (raw)
In-Reply-To: <87o98wpqna.fsf@arm.com>
> I did it that way so that it would be easy to add things like
> zero_or_minus_onep without cut-&-pasting the whole structure.
Yes, I inferred that, but people can still templatize afterward if need be.
Following this line of reasoning, why to limit yourself to this arbitrary
number of 2 values in the template, I'm sure one can imagine the need in some
distant future for initializer_each_minus_one_or_zero_or_onep. ;-)
--
Eric Botcazou
prev parent reply other threads:[~2019-01-04 12:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 11:43 Richard Sandiford
2019-01-04 12:04 ` Eric Botcazou
2019-01-04 12:13 ` Richard Sandiford
2019-01-04 12:19 ` Jakub Jelinek
2019-01-04 12:44 ` Richard Sandiford
2019-01-07 11:35 ` Richard Biener
2019-01-04 12:25 ` Eric Botcazou [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=1764423.ZT9OE2iC5R@polaris \
--to=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.sandiford@arm.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).