public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: Jan-Benedict Glaw <jbglaw@lug-owl.de>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [gdb/build] Fix Werror=nonnull-compare build breaker with gcc 12
Date: Wed, 28 Jul 2021 17:31:56 +0200	[thread overview]
Message-ID: <5bfd6fbc-b97b-fad3-c7a5-87fb4ce97318@suse.de> (raw)
In-Reply-To: <20210728092832.GA8980@embecosm.com>

On 7/28/21 11:28 AM, Andrew Burgess wrote:
> Sorry, I missed that the thread had moved to the patches list.
> 

Np, happens to me all the time :)

> Using trunk GCC I see a warning like this:
> 
>   error: 'volatile'-qualified return type is deprecated [-Werror=volatile]
>      21 | const T * volatile
>         | ^~~~~
>   cc1plus: all warnings being treated as errors
>   Compiler returned: 1
> 
> See: https://godbolt.org/z/nfhq6zb7q
> 

I could reproduce that after adding -std=c++20.  Thanks for finding
that, I had no idea about certain uses of volatile being deprecated.

I've looked a bit further into things today, and submitted
"[PATCH][gcc/doc] Improve nonnull attribute documentation" (
https://gcc.gnu.org/pipermail/gcc-patches/2021-July/576218.html ) .

Let's see if we get any useful feedback there.

Thanks,
- Tom

  reply	other threads:[~2021-07-28 15:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210726211101.ivychvbfgaafxjtz@lug-owl.de>
     [not found] ` <20210727100354.GB4037238@embecosm.com>
     [not found]   ` <b29d9d0b-f847-c0a0-9f09-d42d0f5e91df@suse.de>
     [not found]     ` <20210727113511.GC4037238@embecosm.com>
     [not found]       ` <6cf80ba9-b010-bb42-c92d-84e4f396813c@suse.de>
     [not found]         ` <b4da20e9-69a0-8b92-606d-ddf858539a66@suse.de>
2021-07-27 16:28           ` Tom de Vries
2021-07-28  9:28             ` Andrew Burgess
2021-07-28 15:31               ` Tom de Vries [this message]
2021-07-28 16:15             ` Tom Tromey
2021-07-28 22:32             ` Tom de Vries
2021-07-29 11:42               ` [master + 11][gdb/build] Disable attribute nonnull Tom de Vries
2021-07-29 17:30                 ` Tom Tromey
2021-07-30 10:16                 ` Andrew Burgess

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=5bfd6fbc-b97b-fad3-c7a5-87fb4ce97318@suse.de \
    --to=tdevries@suse.de \
    --cc=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jbglaw@lug-owl.de \
    /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).