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++/64814] std::copy_n advances InputIterator one *less* time than necessary.
Date: Tue, 27 Jan 2015 17:06:00 -0000	[thread overview]
Message-ID: <bug-64814-4-R1f1aAeU9v@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64814-4@http.gcc.gnu.org/bugzilla/>

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Anquietas from comment #5)
> "Effects: For each non-negative integer i < n, performs *(result + i) =
> *(first + i)."
> Since it's talking about input iterators where (first + n) isn't valid I

See 25.1 [algorithms.general] p12.

> think we can interpret this as n applications each of ++first and *first.

No, i < n so (first+n) is not needed and only n-1 applications of ++first are
required. It is unspecified whether the algorithm increments the iterator again
after the last write, but at least two implementations do not perform that
final increment.

So I'm closing this as not a bug. If
http://cplusplus.github.io/LWG/lwg-active.html#2242 becomes a defect and
changes something we will make whatever change is needed, but I don't think we
have a bug now in libstdc++.


  parent reply	other threads:[~2015-01-27 17:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27  3:49 [Bug libstdc++/64814] New: " alex-j-a at hotmail dot co.uk
2015-01-27 11:28 ` [Bug libstdc++/64814] " redi at gcc dot gnu.org
2015-01-27 16:06 ` redi at gcc dot gnu.org
2015-01-27 16:09 ` alex-j-a at hotmail dot co.uk
2015-01-27 16:18 ` redi at gcc dot gnu.org
2015-01-27 16:29 ` redi at gcc dot gnu.org
2015-01-27 16:40 ` alex-j-a at hotmail dot co.uk
2015-01-27 16:51 ` alex-j-a at hotmail dot co.uk
2015-01-27 17:06 ` redi at gcc dot gnu.org [this message]
2015-01-28 13:40 ` redi at gcc dot gnu.org
2015-01-29 21:06 ` alex-j-a at hotmail dot co.uk

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-64814-4-R1f1aAeU9v@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).