public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/101831] [11/12 Regression] Spurious maybe-uninitialized warning on std::array::size
Date: Wed, 02 Feb 2022 00:22:11 +0000 [thread overview]
Message-ID: <bug-101831-4-AeQ047pVp5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101831-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101831
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Sebor <msebor@gcc.gnu.org>:
https://gcc.gnu.org/g:756eabacfcd767e39eea63257a026f61a4c4e661
commit r12-6992-g756eabacfcd767e39eea63257a026f61a4c4e661
Author: Martin Sebor <msebor@redhat.com>
Date: Tue Feb 1 17:19:11 2022 -0700
Declare std::array members with attribute const [PR101831].
Resolves:
PR libstdc++/101831 - Spurious maybe-uninitialized warning on
std::array::size
libstdc++-v3/ChangeLog:
PR libstdc++/101831
* include/std/array (begin): Declare const member function
attribute
const.
(end, rbegin, rend, size, max_size, empty, data): Same.
* testsuite/23_containers/array/capacity/empty.cc: Add test cases.
* testsuite/23_containers/array/capacity/max_size.cc: Same.
* testsuite/23_containers/array/capacity/size.cc: Same.
* testsuite/23_containers/array/iterators/begin_end.cc: New test.
next prev parent reply other threads:[~2022-02-02 0:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 16:13 [Bug c++/101831] New: " m101010a at gmail dot com
2021-08-16 19:18 ` [Bug tree-optimization/101831] " msebor at gcc dot gnu.org
2022-01-21 21:32 ` kim.walisch at gmail dot com
2022-01-24 21:31 ` [Bug tree-optimization/101831] [11/12 Regression] " msebor at gcc dot gnu.org
2022-01-27 21:34 ` msebor at gcc dot gnu.org
2022-01-28 2:03 ` pinskia at gcc dot gnu.org
2022-02-01 18:54 ` msebor at gcc dot gnu.org
2022-02-02 0:22 ` cvs-commit at gcc dot gnu.org [this message]
2022-02-02 0:24 ` [Bug tree-optimization/101831] [11 " msebor at gcc dot gnu.org
2022-04-21 7:50 ` rguenth at gcc dot gnu.org
2023-05-29 10:05 ` jakub at gcc dot gnu.org
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=bug-101831-4-AeQ047pVp5@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).