Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 6/8] const-fy regcache::m_aspace
Date: Wed, 01 Nov 2017 14:00:00 -0000	[thread overview]
Message-ID: <7f4bb93d7518f57556791bb93aad6360@polymtl.ca> (raw)
In-Reply-To: <86d152xrl0.fsf@gmail.com>

On 2017-11-01 05:42, Yao Qi wrote:
> Simon Marchi <simon.marchi@ericsson.com> writes:
> 
>> I don't really understand what this patch tries to achieve.  From the
>> description above, I thought you wanted to make the m_aspace field 
>> const,
>> not the pointed object.
>> 
> 
> I want to achieve both, the field m_aspace is a const, and the pointed
> object is const too.
> 
>    /* The address space of this register cache (for registers where it
>       makes sense, like PC or SP).  */
> -  struct address_space *m_aspace;
> +  const address_space * const m_aspace;

Ah ok I had missed that there was two consts added.

>> If constifying the pointed address_space object is really what you 
>> meant to
>> do, I find having the const_cast more confusing than anything else.  I 
>> think
>> we should constify all the way (removing const_casts, putting more 
>> consts
>> where needed) or not at all.
> 
> OK, const_cast is removed in the updated patch, what do you think?

LGTM!


  reply	other threads:[~2017-11-01 14:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-27  9:31 [PATCH 0/8] regcache misc cleanup and refactor Yao Qi
2017-10-27  9:31 ` [PATCH 3/8] New method regcache::assert_regnum Yao Qi
2017-10-27  9:31 ` [PATCH 4/8] Remove regcache_descr::nr_raw_registers Yao Qi
2017-10-31 14:27   ` Simon Marchi
2017-11-02 15:20     ` Yao Qi
2017-10-27  9:31 ` [PATCH 1/8] Remove regcache_descr fields sizeof_raw_register_status and sizeof_cooked_register_status Yao Qi
2017-10-27  9:32 ` [PATCH 6/8] const-fy regcache::m_aspace Yao Qi
2017-10-31 14:19   ` Simon Marchi
2017-11-01  9:43     ` Yao Qi
2017-11-01 14:00       ` Simon Marchi [this message]
2017-11-01 14:35         ` Yao Qi
2017-10-27  9:32 ` [PATCH 7/8] const-fy regcache::m_readonly_p Yao Qi
2017-10-27  9:32 ` [PATCH 8/8] Construct readonly regcache without address space Yao Qi
2017-10-31 14:35   ` Simon Marchi
     [not found]     ` <CAH=s-PMFXtwS-3J9et_onyEOCUL9P-AgO9V=pBt60neQn67g9g@mail.gmail.com>
2017-10-31 18:04       ` Simon Marchi
2017-10-27  9:32 ` [PATCH 5/8] s/get_regcache_aspace (regcache)/regcache->aspace ()/g Yao Qi
2017-10-27  9:32 ` [PATCH 2/8] Remove code wrapped by "#if 0" Yao Qi

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=7f4bb93d7518f57556791bb93aad6360@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=qiyaoltc@gmail.com \
    --cc=simon.marchi@ericsson.com \
    /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