From: Shubham Narlawar <gsocshubham@gmail.com>
To: GCC Development <gcc@gcc.gnu.org>
Subject: Ferching Rtl instruction corressponding to Gimple Call instruction
Date: Tue, 12 Apr 2022 00:49:16 +0530 [thread overview]
Message-ID: <CAN=hqDA+d6XTPLw5Uu1zuz7RmPC_Csto9EkPLnG-Zo0JafbJaA@mail.gmail.com> (raw)
Hello,
I want to collect complete rtl instruction corresponding to below gimple
call - "__builtin_temp"
I have gimple instructions of form -
slli_31 = _2 << 8;
srli_32 = slli_31 >> 8;
add_33 = srli_32 + 15;
_20 = __builtin_temp (instrn_buffer.36_1, 1, add_33);
For that, I put breakpoint in expand_call() present in cfgexpand.c. I
traced the execution from expand_call() and found out that the last filled
rtl instruction is present at end of expand_assignment(). Is my
understanding correct?
I am getting rtl instructions of form -
(reg:V64SF 100 [ _16 ])
or
(reg:V64SF 69 L3 [orig:100 _16 ] [100])
From above rtl insn dumps, it is clear that it does not represent complete
information of gimple call - _20 = __builtin_temp (instrn_buffer.36_1, 1,
add_33);
Where can I get complete RTL instruction such that I would be able to
extract operands like fld[4], fld[5]?
Thanks and Regards,
Shubham
reply other threads:[~2022-04-11 19:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAN=hqDA+d6XTPLw5Uu1zuz7RmPC_Csto9EkPLnG-Zo0JafbJaA@mail.gmail.com' \
--to=gsocshubham@gmail.com \
--cc=gcc@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).