Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Luis Machado <luis.machado@linaro.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH] trad-frame cleanups
Date: Tue, 19 Jan 2021 10:22:53 -0500	[thread overview]
Message-ID: <059e1efb-fc68-75ce-43ef-76ae4157d93c@polymtl.ca> (raw)
In-Reply-To: <20210119142014.1949161-1-luis.machado@linaro.org>



On 2021-01-19 9:20 a.m., Luis Machado via Gdb-patches wrote:
> With the new member functions for struct trad_frame_saved_reg, there is no
> need to invoke some of the set/get functions anymore.  This patch removes
> those and adjusts all callers.
> 
> Even though the most natural initial state of a saved register value is
> UNKNOWN, there are target backends relying on the previous initial state
> of REALREG set to a register's own number. I noticed this in at least a
> couple targets: aarch64 and riscv.
> 
> Because of that, I decided to keep the reset function that sets the set of
> register values to REALREG. I can't exercise all the targets to make sure
> the initial state change won't break things, hence why it is risky to change
> the default.
> 
> Validated with --enable-targets=all on aarch64-linux Ubuntu 18.04/20.04.
> 
> Thoughts?

I did a spot check on a few files, and that LGTM, thanks!

Simon

  reply	other threads:[~2021-01-19 15:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-19 14:20 Luis Machado via Gdb-patches
2021-01-19 15:22 ` Simon Marchi via Gdb-patches [this message]
2021-01-19 17:44   ` Luis Machado via Gdb-patches

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=059e1efb-fc68-75ce-43ef-76ae4157d93c@polymtl.ca \
    --to=gdb-patches@sourceware.org \
    --cc=luis.machado@linaro.org \
    --cc=simon.marchi@polymtl.ca \
    /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