Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Saagar Jha <saagar@saagarjha.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Add a missing munmap_list move constructor
Date: Fri, 25 Sep 2020 10:58:48 -0400	[thread overview]
Message-ID: <b2803436-d746-9e5f-303f-e809a6d9ead3@simark.ca> (raw)
In-Reply-To: <20200925070525.47993-1-saagar@saagarjha.com>

On 2020-09-25 3:05 a.m., Saagar Jha wrote:
> compile_module attempts to request a move constructor, but because
> munmap_list doesn't have one it gets implicitly deleted. This is an
> warning on clang under -Wdefaulted-function-deleted (which is enabled by
> default):
>
> In file included from compile/compile-object-load.c:21:
> compile/compile-object-load.h:56:3: error: explicitly defaulted move constructor is implicitly deleted [-Werror,-Wdefaulted-function-deleted]
>   compile_module (compile_module &&other) = default;
>   ^
> compile/compile-object-load.h:86:22: note: move constructor of 'compile_module' is implicitly deleted because field 'munmap_list' has a deleted move constructor
>   struct munmap_list munmap_list;
>                      ^
> compile/compile-object-load.h:30:28: note: 'munmap_list' has been explicitly marked deleted here
>   DISABLE_COPY_AND_ASSIGN (munmap_list);
>                            ^
>
> gdb/ChangeLog:
>
> 	* compile/compile-object-load.h: Give munmap_list a move
> 	constructor.

Thanks, I pushed it.  FYI, I tweaked the ChangeLog entry to include the
structure name in parenthesis:

	* compile/compile-object-load.h (struct munmap_list): Add
	explicitly-defined move constructor.

Simon

  parent reply	other threads:[~2020-09-25 14:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-24  5:22 Saagar Jha
2020-09-24 15:27 ` Simon Marchi
2020-09-25  6:59   ` Saagar Jha
2020-09-25  7:05     ` Saagar Jha
2020-09-25  7:05       ` Saagar Jha
2020-09-25 14:58       ` Simon Marchi [this message]
2020-09-26  0:25         ` Saagar Jha

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=b2803436-d746-9e5f-303f-e809a6d9ead3@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=saagar@saagarjha.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