From: Mauro Ziliani <mauro@faresoftware.it>
To: gcc-help@gnu.org
Subject: How to avoid this warning at /usr/include/c++/10/bits/stl_uninitialized.h:84:9
Date: Wed, 9 Feb 2022 17:22:01 +0100 [thread overview]
Message-ID: <74633bf8-720c-245b-a3cc-75e6467c145e@faresoftware.it> (raw)
Good morning.
I'm working with gcc (Raspbian 10.2.1-6+rpi1) 10.2.1 20210110 and boost
1.75.0 and CMake
When I compile some sources I get this warning
/usr/include/c++/10/bits/stl_uninitialized.h:84:9: note: parameter
passing for argument of type
‘std::move_iterator<boost::asio::detail::timer_queue<boost::asio::detail::chrono_time_traits<std::chrono::_V2::steady_clock,
boost::asio::wait_traits<std::chrono::_V2::steady_clock> >
>::heap_entry*>’ changed in GCC 7.1
It is tedious to see this every time.
How can I avoid this?
I set(CXX_STANDARD 11) in CMakeLists.txt
Thanks all
MZ
next reply other threads:[~2022-02-09 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 16:22 Mauro Ziliani [this message]
2022-02-09 20:17 ` Jonathan Wakely
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=74633bf8-720c-245b-a3cc-75e6467c145e@faresoftware.it \
--to=mauro@faresoftware.it \
--cc=gcc-help@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).