From: Erick Ochoa <eochoa@gcc.gnu.org>
To: gcc@gcc.gnu.org
Subject: Question on updating function body on specialized functions
Date: Tue, 8 Mar 2022 14:53:29 +0100 [thread overview]
Message-ID: <CAJ_nqzgjpf_s97TUAMp84jpGJsZuxJiydC_hY2-55yWi1wZB6A@mail.gmail.com> (raw)
Hi,
I have one function (F) that has been specialized for two different calling
contexts (F1 and F2) and two late SIMPLE_IPA_PASSes (A and B). Pass A
changes some MEM_REFs such that the type of MEM_REF is compatible with the
type of the first operand of the expression. Pass A changes both F1 and F2.
I have printed the function bodies of both F1 and F2 during Pass A and
everything looks correct. Pass B uses these changes.
However I noticed this interesting behaviour:
1. If I fix F1 first and then F2, then pass B will see F2 correctly but
some of F1 MEM_REFs will be incorrect.
2. If I fix F2 first and then F1, then pass B will see F1 correctly but
some of F2 MEM_REFs will be incorrect.
My question is do different specialized functions share the same trees? How
would I then change the bodies of specialized functions?
Thanks!
next reply other threads:[~2022-03-08 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 13:53 Erick Ochoa [this message]
2022-03-08 14:51 ` Martin Jambor
2022-03-08 15:29 ` Erick Ochoa
2022-03-08 22:11 ` Gary Oblock
2022-03-09 8:36 ` Richard Biener
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=CAJ_nqzgjpf_s97TUAMp84jpGJsZuxJiydC_hY2-55yWi1wZB6A@mail.gmail.com \
--to=eochoa@gcc.gnu.org \
--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).