public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/67374] std::cbegin can't call valarray range access functions
Date: Thu, 03 Sep 2015 15:11:00 -0000	[thread overview]
Message-ID: <bug-67374-4-EBXqvYhLzy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67374-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67374

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Thu Sep  3 15:10:42 2015
New Revision: 227454

URL: https://gcc.gnu.org/viewcvs?rev=227454&root=gcc&view=rev
Log:
Backport libstdc++/67374 fix from mainline

2015-08-27  Jonathan Wakely  <jwakely@redhat.com>

        PR libstdc++/67374
        * include/bits/range_access.h (valarray, begin, end): Declare.
        * testsuite/26_numerics/valarray/range_access.cc: Test const
        overloads.
        * testsuite/26_numerics/valarray/range_access2.cc: New.

Added:
   
branches/gcc-5-branch/libstdc++-v3/testsuite/26_numerics/valarray/range_access2.cc
      - copied, changed from r227453,
branches/gcc-5-branch/libstdc++-v3/testsuite/26_numerics/valarray/range_access.cc
Modified:
    branches/gcc-5-branch/libstdc++-v3/ChangeLog
    branches/gcc-5-branch/libstdc++-v3/include/bits/range_access.h
   
branches/gcc-5-branch/libstdc++-v3/testsuite/26_numerics/valarray/range_access.cc


  parent reply	other threads:[~2015-09-03 15:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-27 17:34 [Bug libstdc++/67374] New: " redi at gcc dot gnu.org
2015-08-27 17:34 ` [Bug libstdc++/67374] " redi at gcc dot gnu.org
2015-08-27 18:43 ` redi at gcc dot gnu.org
2015-08-27 19:05 ` redi at gcc dot gnu.org
2015-09-03 15:11 ` redi at gcc dot gnu.org [this message]
2015-09-03 15:12 ` 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-67374-4-EBXqvYhLzy@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).