public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "adrien.hamelin+gcc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/61597] Unexpected behavior at runtime
Date: Wed, 25 Jun 2014 08:22:00 -0000	[thread overview]
Message-ID: <bug-61597-4-jyCldqdHDK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61597-4@http.gcc.gnu.org/bugzilla/>

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

Adrien Hamelin <adrien.hamelin+gcc at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #33000|0                           |1
        is obsolete|                            |

--- Comment #8 from Adrien Hamelin <adrien.hamelin+gcc at gmail dot com> ---
Created attachment 33002
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33002&action=edit
Preprocessed file

Effectively the problem can be showed with much less code lines. I just did a
custom iterator to show the problem (and removed my own array).

The problem comes from line 45. If the function takes a copy, it does not work
but if it takes a reference and do the copy inside (as shown line 52) it does
work.

Once again it works fine with Visual 2013.

The new code : http://coliru.stacked-crooked.com/a/e33afe532e7f1e55


  parent reply	other threads:[~2014-06-25  8:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24 17:18 [Bug c++/61597] New: " adrien.hamelin+gcc at gmail dot com
2014-06-24 18:00 ` [Bug c++/61597] " adrien.hamelin+gcc at gmail dot com
2014-06-25  6:47 ` adrien.hamelin+gcc at gmail dot com
2014-06-25  6:57 ` trippels at gcc dot gnu.org
2014-06-25  8:22 ` adrien.hamelin+gcc at gmail dot com [this message]
2014-06-25  8:36 ` adrien.hamelin+gcc at gmail dot com
2014-06-25 10:03 ` redi at gcc dot gnu.org
2014-06-25 10:12 ` redi at gcc dot gnu.org
2014-06-25 11:30 ` adrien.hamelin+gcc at gmail dot com
2014-06-25 12:16 ` redi at gcc dot gnu.org
2014-06-25 13:00 ` glisse at gcc dot gnu.org
2014-06-25 13:08 ` redi at gcc dot gnu.org
2014-06-25 13:23 ` glisse at gcc dot gnu.org
2014-06-25 16:56 ` manu at gcc dot gnu.org
2014-06-25 20:31 ` glisse at gcc dot gnu.org
2023-01-31  3:35 ` pinskia 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-61597-4-jyCldqdHDK@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).