From: Jeff Law <jeffreyalaw@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 1/2] cselib: Keep track of further subvalue relations
Date: Tue, 27 Sep 2022 17:46:32 -0600 [thread overview]
Message-ID: <95d6fcc6-846c-d484-fda7-1eeeabca87e7@gmail.com> (raw)
In-Reply-To: <20220907142026.936922-2-stefansf@linux.ibm.com>
On 9/7/22 08:20, Stefan Schulze Frielinghaus via Gcc-patches wrote:
> Whenever a new cselib value is created check whether a smaller value
> exists which is contained in the bigger one. If so add a subreg
> relation to locs of the smaller one.
>
> gcc/ChangeLog:
>
> * cselib.cc (new_cselib_val): Keep track of further subvalue
> relations.
OK
jeff
next prev parent reply other threads:[~2022-09-27 23:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 14:20 [PATCH 0/2] Variable tracking and subvalues Stefan Schulze Frielinghaus
2022-09-07 14:20 ` [PATCH 1/2] cselib: Keep track of further subvalue relations Stefan Schulze Frielinghaus
2022-09-26 6:10 ` Stefan Schulze Frielinghaus
2022-09-27 23:46 ` Jeff Law [this message]
2022-09-29 17:40 ` Joseph Myers
2022-09-07 14:20 ` [PATCH 2/2] var-tracking: Add entry values up to max register mode Stefan Schulze Frielinghaus
2022-09-26 6:10 ` Stefan Schulze Frielinghaus
2022-09-27 23:44 ` Jeff Law
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=95d6fcc6-846c-d484-fda7-1eeeabca87e7@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@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).