From: navya deepika Garakapati <navyadeepika.garakapati@gmail.com>
To: gcc@gcc.gnu.org
Cc: rguenth@gcc.gnu.org
Subject: Regarding Bug 85539 - x86_64: loads are not always narrowed [https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85539]
Date: Mon, 06 May 2019 06:57:00 -0000 [thread overview]
Message-ID: <CAF4caZ3RjkOrB1M1URHAJANzVNWhHH46m2sjPGvjH-UVPW=7NA@mail.gmail.com> (raw)
Hi All,
For the below testcase,
$cat test.c
int foo(long *p)
{
return *p;
}
when compile with clang -O2
$clang test.c -O2 -S
$cat test.s
foo:
movl (%rdi), %eax
retq
while gcc gives
$gcc test.c -O2 -S
$cat test.s
foo:
movq (%rdi), %rax
retq
As you can see the difference clang is loading value in eax(32 bit) while
gcc uses rax(64 bit).
While analysing it we found that ,
In gcc trunck with -O0 optimization,
we can notice that in ira pass, there is a conversion information from
64bit to 32bit (subreg:SI (reg:DI 82 [ _1 ]) 0)):
ira pass:
(insn 8 7 11 2 (set (reg:SI 83 [ _4 ])
(subreg:SI (reg:DI 82 [ _1 ]) 0)) "t.c":3:8 67 {*movsi_internal}
(expr_list:REG_DEAD (reg:DI 82 [ _1 ])
(nil)))
while reload pass is deleting this information and assigning 32bit to 32bit
i.e; SI to SI which results this as a dead code for the next pass and as a
result this insn 8 is getting deleted in next pass which is split2 pass.
reload pass:
(insn 8 7 15 2 (set (reg:SI 0 ax [orig:83 _4 ] [83])
(reg:SI 0 ax [orig:82 _1 ] [82])) "t.c":3:8 67 {*movsi_internal}
(nil))
We would like to know why conversion from DI to SI is converted to SI to
SI in reload pass (which uses any target hook).
Thanks & Regards
Navya.
next reply other threads:[~2019-05-06 6:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 6:57 navya deepika Garakapati [this message]
2019-05-20 7:36 navya deepika Garakapati
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='CAF4caZ3RjkOrB1M1URHAJANzVNWhHH46m2sjPGvjH-UVPW=7NA@mail.gmail.com' \
--to=navyadeepika.garakapati@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=rguenth@gcc.gnu.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).