From: Jakub Jelinek <jakub@redhat.com>
To: Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org, Jan Hubicka <jh@suse.de>
Subject: Re: [PATCH] Fix PR84986
Date: Tue, 20 Mar 2018 13:36:00 -0000 [thread overview]
Message-ID: <20180320104629.GA8577@tucnak> (raw)
In-Reply-To: <alpine.LSU.2.20.1803201127490.18265@zhemvz.fhfr.qr>
On Tue, Mar 20, 2018 at 11:41:01AM +0100, Richard Biener wrote:
> If the precision matches the mode maybe. But I thought we try to
> avoid using %al (HImode) or %ax (QImode) operands in the end?
Yes, but we try to do that only on the level of the emitted assembly,
sometimes we simply emit a QImode or HImode instruction that does
movl %eax, %ebx
and similar. That is also zero cost compared to what it would cost to do it
in SImode.
Jakub
next prev parent reply other threads:[~2018-03-20 13:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 10:35 Richard Biener
2018-03-20 11:37 ` Jakub Jelinek
2018-03-20 10:50 ` Richard Biener
2018-03-20 13:36 ` Jakub Jelinek [this message]
2018-03-20 11:09 ` Richard Biener
2018-03-20 13:53 ` Jan Hubicka
2018-03-24 17:42 ` H.J. Lu
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=20180320104629.GA8577@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jh@suse.de \
--cc=rguenther@suse.de \
/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).