public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ed at edwardrosten dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/51850] debug mode for std::array and tr1::array
Date: Wed, 18 Jan 2012 17:20:00 -0000	[thread overview]
Message-ID: <bug-51850-4-MecKxDmupw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51850-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51850

--- Comment #1 from Edward Rosten <ed at edwardrosten dot com> 2012-01-18 16:35:40 UTC ---
Created attachment 26368
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26368
Adds bounds checking to std::array and tr1::array in debug mode.


I've attached a patch which adds bounds checking to std::array (C++0x) and
std::tr1::array. 

The std::array patch keeps operator[] as constexpr.


  reply	other threads:[~2012-01-18 16:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-13 17:53 [Bug libstdc++/51850] New: " redi at gcc dot gnu.org
2012-01-18 17:20 ` ed at edwardrosten dot com [this message]
2012-03-22 11:02 ` [Bug libstdc++/51850] " paolo.carlini at oracle dot com
2012-11-07  0:42 ` paolo at gcc dot gnu.org
2012-11-07  0:43 ` paolo.carlini at oracle dot com

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-51850-4-MecKxDmupw@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).