public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ville Voutilainen <ville.voutilainen@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Jason Merrill <jason@redhat.com>,
	gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: C++ PATCH for c++/88136, -Wdeprecated-copy too noisy
Date: Sat, 08 Dec 2018 17:17:00 -0000	[thread overview]
Message-ID: <CAFk2RUYYLv-YguwazLTCxQMHwxDQRivVKqj_rxn4cr1eKLC1dw@mail.gmail.com> (raw)
In-Reply-To: <20181208165817.GU12380@tucnak>

On Sat, 8 Dec 2018 at 18:58, Jakub Jelinek <jakub@redhat.com> wrote:
> > g++ -c -pipe -O2 -fPIC -std=c++1z -fvisibility=hidden
> > -fvisibility-inlines-hidden -ffunction-sections -fdata-sections
> > -fno-exceptions -Wall -W -Wvla -Wdate-time -Wshift-overflow=2
>
> -W is an alias to -Wextra.

Yeah. Jason, I seem to have code that user-provides a copy constructor
(seemingly for no particular reason),
doesn't bother declaring a copy assignment operator, and still breaks
magnificently. :) There is no bug
in it; the assignment works as expected, so that's a false positive. I
am going to suggest taking this warning
out of -Wextra and making it completely separate for GCC 9.

  reply	other threads:[~2018-12-08 17:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-06 21:12 Jason Merrill
2018-12-08 16:46 ` Ville Voutilainen
2018-12-08 16:58   ` Jakub Jelinek
2018-12-08 17:17     ` Ville Voutilainen [this message]
2018-12-08 17:53       ` Jason Merrill
2018-12-08 18:05         ` Ville Voutilainen
2018-12-08 18:33           ` Ville Voutilainen
2018-12-12 14:52             ` Jason Merrill
2018-12-12 15:30               ` Ville Voutilainen

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=CAFk2RUYYLv-YguwazLTCxQMHwxDQRivVKqj_rxn4cr1eKLC1dw@mail.gmail.com \
    --to=ville.voutilainen@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=jason@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).