From: Yao Qi <qiyaoltc@gmail.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Add macro DISABLE_COPY_AND_ASSIGN
Date: Wed, 02 Aug 2017 11:19:00 -0000 [thread overview]
Message-ID: <CAH=s-POK+LNJLCo8LrMRBJmDyhrGFxsCL-XDGajJfevFn5MSOw@mail.gmail.com> (raw)
In-Reply-To: <20170726085510.GA8039@1170ee0b50d5>
On Wed, Jul 26, 2017 at 9:55 AM, Yao Qi <qiyaoltc@gmail.com> wrote:
> On 17-07-19 10:30:45, Yao Qi wrote:
>> We have many classes that copy cotr and assignment operator are deleted
>> in different projects, gcc, gdb and gold. So this patch adds a macro
>> to do this, and replace these existing mechanical code with macro
>> DISABLE_COPY_AND_ASSIGN.
>>
>> The patch was posted in gdb-patches,
>> https://sourceware.org/ml/gdb-patches/2017-07/msg00254.html but we
>> think it is better to put this macro in include/ansidecl.h so that
>> other projects can use it too.
>>
>> Boostrapped on x86_64-linux-gnu. Is it OK?
>>
>> include:
>>
>> 2017-07-19 Yao Qi <yao.qi@linaro.org>
>> Pedro Alves <palves@redhat.com>
>>
>> * ansidecl.h (DISABLE_COPY_AND_ASSIGN): New macro.
>>
>> gcc/cp:
>>
>> 2017-07-19 Yao Qi <yao.qi@linaro.org>
>>
>> * cp-tree.h (class ovl_iterator): Use DISABLE_COPY_AND_ASSIGN.
>> * name-lookup.c (struct name_loopup): Likewise.
>>
>> gcc:
>>
>> 2017-07-19 Yao Qi <yao.qi@linaro.org>
>>
>> * tree-ssa-scopedtables.h (class avail_exprs_stack): Use
>> DISABLE_COPY_AND_ASSIGN.
>> (class const_and_copies): Likewise.
>
> Ping.
> https://gcc.gnu.org/ml/gcc-patches/2017-07/msg01134.html
>
Ping. It is a quite straightforward patch, can any one
take a look?
--
Yao (齐尧)
next prev parent reply other threads:[~2017-08-02 11:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 9:31 Yao Qi
2017-07-26 8:55 ` Yao Qi
2017-08-02 11:19 ` Yao Qi [this message]
2017-08-11 15:38 ` Pedro Alves
2017-09-09 9:45 ` Yao Qi
2017-09-09 12:27 ` Ian Lance Taylor
2017-09-15 15:44 ` 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='CAH=s-POK+LNJLCo8LrMRBJmDyhrGFxsCL-XDGajJfevFn5MSOw@mail.gmail.com' \
--to=qiyaoltc@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).