public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "arnaud02 at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/98518] New: std::array not bound checked with _GLIBCXX_ASSERTIONS Date: Mon, 04 Jan 2021 21:34:51 +0000 [thread overview] Message-ID: <bug-98518-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98518 Bug ID: 98518 Summary: std::array not bound checked with _GLIBCXX_ASSERTIONS Product: gcc Version: 10.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: arnaud02 at users dot sourceforge.net Target Milestone: --- operator[] of std::array is not bound checked when specifying _GLIBCXX_ASSERTIONS. Considering: #define _GLIBCXX_ASSERTIONS 1 #include <array> #include <cstdio> int f(int i) { std::array<int,2> x = {1, 4}; return x[i]; // bounds are not checked } int main() { volatile int i = 2; printf("f=%d\n", f(i)); } the array bound violation is not detected. By constrast, replacing std::array by std::vector results in the expected assertion violation.
next reply other threads:[~2021-01-04 21:34 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-04 21:34 arnaud02 at users dot sourceforge.net [this message] 2021-01-05 13:32 ` [Bug libstdc++/98518] " redi at gcc dot gnu.org 2021-01-06 10:23 ` arnaud02 at users dot sourceforge.net 2021-07-22 13:41 ` redi 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-98518-4@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: linkBe 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).