From: "H.J. Lu" <hjl.tools@gmail.com>
To: Michael Zolotukhin <michael.v.zolotukhin@gmail.com>
Cc: Jan Hubicka <hubicka@ucw.cz>, Uros Bizjak <ubizjak@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, x86] Use vector moves in memmove expanding
Date: Tue, 14 May 2013 15:55:00 -0000 [thread overview]
Message-ID: <CAMe9rOqFkoxz0dBguGkFJSifvrE9HkNr_Ff75NSbgBO+mLZOdw@mail.gmail.com> (raw)
In-Reply-To: <CANtU078+7ZDTqntod8t+4KCGyHH15WW9SQUqQa82N_WRYnxHMw@mail.gmail.com>
On Tue, May 14, 2013 at 7:34 AM, Michael Zolotukhin
<michael.v.zolotukhin@gmail.com> wrote:
> Hi,
> I attached an updated version of the patch. Looks like the 64-bit issue is
> resolved in it (now a vector mode is explicitly chosen instead of TI- or
> another integer mode). Also, some of remarks are fixed in it - some
> others are still not changed, because I don't know what to do with them right
> now (see my questions in the previous letter).
>
> Could you take a look at the patch?
>
> I checked it on i386/x86_64 bootstrap and make check, and on Specs2000/2006
> (I checked only stability).
>
You use Pmode as the largest integer mode. Is word_mode better
than Pmode since word_mode is DI and Pmode may be SI for x32.
--
H.J.
next prev parent reply other threads:[~2013-05-14 15:55 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 17:54 Michael Zolotukhin
2013-04-10 20:17 ` Ondřej Bílka
2013-04-10 21:39 ` Michael Zolotukhin
2013-04-10 22:24 ` Ondřej Bílka
2013-04-11 12:56 ` Michael Zolotukhin
2013-04-12 10:06 ` Ondřej Bílka
2013-04-12 11:10 ` Michael Zolotukhin
2013-04-13 18:13 ` Ondřej Bílka
2013-04-17 16:18 ` Jan Hubicka
2013-04-17 18:40 ` Jan Hubicka
2013-04-18 13:50 ` Michael Zolotukhin
2013-04-18 13:55 ` Michael Zolotukhin
2013-05-14 14:35 ` Michael Zolotukhin
2013-05-14 15:55 ` H.J. Lu [this message]
2013-05-15 12:47 ` Michael Zolotukhin
2013-05-15 15:45 ` H.J. Lu
2013-06-05 14:10 ` Michael Zolotukhin
2013-06-20 13:16 ` Michael Zolotukhin
2013-06-20 16:56 ` Michael Zolotukhin
2013-06-25 13:36 ` Michael Zolotukhin
2013-06-30 9:06 ` Uros Bizjak
2013-06-30 9:32 ` Jan Hubicka
2013-06-30 19:15 ` Ondřej Bílka
2013-07-02 14:37 ` Michael Zolotukhin
2013-07-05 7:58 ` Michael Zolotukhin
2013-07-05 11:25 ` Jan Hubicka
2013-07-08 6:49 ` Kirill Yukhin
2013-07-08 6:56 ` Michael Zolotukhin
2013-09-03 19:01 ` Eric Botcazou
2013-09-03 19:05 ` Michael V. Zolotukhin
2013-09-03 19:25 ` H.J. Lu
2013-09-06 16:58 ` H.J. Lu
2013-09-06 20:50 ` Michael Zolotukhin
2013-09-09 7:35 ` Michael V. Zolotukhin
2013-09-09 7:40 ` Jan Hubicka
2013-09-09 7:46 ` Michael V. Zolotukhin
2013-09-09 7:46 ` Uros Bizjak
2013-09-09 7:59 ` Jakub Jelinek
2013-09-09 8:01 ` Michael V. Zolotukhin
2013-09-09 8:02 ` Jakub Jelinek
2013-09-09 9:19 ` Michael V. Zolotukhin
2013-09-09 9:24 ` Jakub Jelinek
2013-09-09 9:25 ` Michael V. Zolotukhin
2013-09-09 9:32 ` Uros Bizjak
2013-09-09 10:13 ` Michael V. Zolotukhin
2013-09-09 10:19 ` Jakub Jelinek
2013-09-09 10:22 ` Uros Bizjak
2013-09-09 10:19 ` Uros Bizjak
2013-09-09 10:27 ` Michael V. Zolotukhin
2013-09-09 12:21 ` Uros Bizjak
2013-09-10 8:23 ` Kirill Yukhin
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=CAMe9rOqFkoxz0dBguGkFJSifvrE9HkNr_Ff75NSbgBO+mLZOdw@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=michael.v.zolotukhin@gmail.com \
--cc=ubizjak@gmail.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).