public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ville.voutilainen at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/61856] New: Ternary operator in an NSDMI causes double evaluation
Date: Sun, 20 Jul 2014 12:18:00 -0000	[thread overview]
Message-ID: <bug-61856-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 61856
           Summary: Ternary operator in an NSDMI causes double evaluation
           Product: gcc
           Version: 4.10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ville.voutilainen at gmail dot com

First test:
#include <iostream>

#ifdef OK
struct ostream { } cout;

bool operator<<(ostream&, const char* s)
{ __builtin_printf("%s", s); return true; }
#else
using std::cout;
#endif

struct X { int a = (cout<<"hmm\n") ? 1 : 2;};

int main()
{
    X x;
}

With -DOK, this prints "hmm" once, otherwise it prints "hmm" twice. This
suggested
that perhaps the problem is specific to iostream, but wrapping the NSDMI into
a lambda fixes the double evaluation:

#include <iostream>

#ifdef OK
struct ostream { } cout;

bool operator<<(ostream&, const char* s)
{ __builtin_printf("%s", s); return true; }
#else
using std::cout;
#endif

struct X { int a = ([]{return bool(cout<<"hmm\n");}()) ? 1 : 2;};

int main()
{
    X x;
}

Simpler cases like just incrementing a global variable in the ternary
operator seem to work fine:

#include <iostream>

int global_x = 0;
struct X { int a = (global_x++) ? 1 : 2;};

int main()
{
    X x;
    std::cout << global_x << std::endl;
}

Perhaps this is some weird gimplification bug.


             reply	other threads:[~2014-07-20 12:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-20 12:18 ville.voutilainen at gmail dot com [this message]
2014-07-20 12:19 ` [Bug c++/61856] " redi at gcc dot gnu.org
2015-06-18 16:50 ` miyuki at gcc dot gnu.org
2015-06-21  9:06 ` ville.voutilainen at gmail 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-61856-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: 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).