From: Gary Oblock <gary@amperecomputing.com>
To: Erick Ochoa <eochoa@gcc.gnu.org>, Martin Jambor <mjambor@suse.cz>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Question on updating function body on specialized functions
Date: Tue, 8 Mar 2022 22:11:29 +0000 [thread overview]
Message-ID: <BYAPR01MB5464D183E0607B2BCAA729C5C6099@BYAPR01MB5464.prod.exchangelabs.com> (raw)
In-Reply-To: <CAJ_nqzhyib_Qu1JpPa0MgKvx_pTsyhwacAbbJSPZ8fqV99Rs4w@mail.gmail.com>
Erick my friend,
That's exactly why I'm such a big fan of creating things
anew each time I mess with them. 😉
Later,
Gary
________________________________
From: Erick Ochoa <eochoa@gcc.gnu.org>
Sent: Tuesday, March 8, 2022 7:29 AM
To: Martin Jambor <mjambor@suse.cz>
Cc: gcc@gcc.gnu.org <gcc@gcc.gnu.org>
Subject: Re: Question on updating function body on specialized functions
Hi Martin!
Thanks for replying, turns out that while I was trying to reply to you I
was able to get the answer. Turns out there is indeed one tree node which
is shared across the two functions. And that is
TREE_OPERAND (MEM_REF, 1).
When I was assigning to
TREE_TYPE ( TREE_OPERAND (MEM_REF, 1) ) in one function, I was modifying
the other. The solution was to create a new tree and assign it directly to
TREE_OPERAND (MEM_REF, 1) in both functions.
Thanks!
next prev parent reply other threads:[~2022-03-08 22:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 13:53 Erick Ochoa
2022-03-08 14:51 ` Martin Jambor
2022-03-08 15:29 ` Erick Ochoa
2022-03-08 22:11 ` Gary Oblock [this message]
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=BYAPR01MB5464D183E0607B2BCAA729C5C6099@BYAPR01MB5464.prod.exchangelabs.com \
--to=gary@amperecomputing.com \
--cc=eochoa@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=mjambor@suse.cz \
/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).