From: Uros Bizjak <ubizjak@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] i386: Use EXT_REX_SSE_REG_P in *movoi_internal_avx/movti_internal
Date: Mon, 11 Feb 2019 13:51:00 -0000 [thread overview]
Message-ID: <CAFULd4YkBBm8fGkAnDrcdopHxGAR-GWWrjARbw13deaj2OOvdw@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOr8+7+VyOa+xwoD3FGg7Jy-Uz+1Tjs72mLDS0_G0YnG+Q@mail.gmail.com>
On Mon, Feb 11, 2019 at 2:29 PM H.J. Lu <hjl.tools@gmail.com> wrote:
> > No. As said, please correctly set mode to XImode in mode attribute calculation.
>
> There is
>
> switch (get_attr_type (insn))
> {
> case TYPE_SSELOG1:
> return standard_sse_constant_opcode (insn, operands);
>
> standard_sse_constant_opcode has
>
> else if (x == constm1_rtx || vector_all_ones_operand (x, mode))
> {
> enum attr_mode insn_mode = get_attr_mode (insn);
>
> switch (insn_mode)
> {
> case MODE_XI:
> case MODE_V8DF:
> case MODE_V16SF:
> gcc_assert (TARGET_AVX512F);
> return "vpternlogd\t{$0xFF, %g0, %g0, %g0|%g0, %g0, %g0, 0xFF}";
If there is something wrong with standard_sse_constant_opcode, then
fix the problem in the function itself. With your previous patch, you
introduced a regression, and the presented fix is another kludge to
fix a stack of kludges inside standard_sse_constant_opcode.
Please take your time and propose some acceptable solution that would
put some logic into const_0/const_1 handling. The situation is not OK
and your patch makes it even worse.
Uros.
next prev parent reply other threads:[~2019-02-11 13:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 21:11 [PATCH] i386: Use OI/TImode in *mov[ot]i_internal_avx with AVX512VL H.J. Lu
2019-02-08 9:51 ` Uros Bizjak
2019-02-08 11:29 ` H.J. Lu
2019-02-09 0:31 ` [PATCH] i386: Use EXT_REX_SSE_REG_P in *movoi_internal_avx/movti_internal H.J. Lu
2019-02-09 9:50 ` Uros Bizjak
2019-02-09 9:56 ` Jakub Jelinek
2019-02-09 10:40 ` Jakub Jelinek
2019-02-09 10:51 ` Jakub Jelinek
2019-02-09 12:12 ` H.J. Lu
2019-02-09 12:22 ` Jakub Jelinek
2019-02-09 13:39 ` Jakub Jelinek
2019-02-11 13:11 ` H.J. Lu
2019-02-11 13:15 ` Uros Bizjak
2019-02-11 13:29 ` H.J. Lu
2019-02-11 13:51 ` Uros Bizjak [this message]
2019-02-11 14:32 ` H.J. Lu
2019-02-11 15:57 ` Uros Bizjak
2019-02-11 16:03 ` H.J. Lu
2019-02-11 16:24 ` Jakub Jelinek
2019-02-14 2:34 ` [PATCH] i386: Properly encode xmm16-xmm31/ymm16-ymm31 for vector move H.J. Lu
2019-02-11 13:47 ` [PATCH] i386: Use EXT_REX_SSE_REG_P in *movoi_internal_avx/movti_internal Jakub Jelinek
2019-02-12 18:03 ` [PATCH] i386: Use OI/TImode in *mov[ot]i_internal_avx with AVX512VL Uros Bizjak
2019-02-12 19:01 ` H.J. Lu
2019-02-11 2:35 ` Alan Modra
2019-02-11 7:23 ` Uros Bizjak
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=CAFULd4YkBBm8fGkAnDrcdopHxGAR-GWWrjARbw13deaj2OOvdw@mail.gmail.com \
--to=ubizjak@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=jakub@redhat.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).