public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "prasoonsaurav.nit at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/51836] New: -Wsequence-point fails when convoluted expressions with multiple side effects are used (C++03)
Date: Thu, 12 Jan 2012 09:11:00 -0000	[thread overview]
Message-ID: <bug-51836-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 51836
           Summary: -Wsequence-point fails when convoluted expressions
                    with multiple side effects are used (C++03)
    Classification: Unclassified
           Product: gcc
           Version: 4.4.6
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: prasoonsaurav.nit@gmail.com


Consider the following example


int main()
{ 
      int i=10;
      i += (i , i++, i) + i; // also invokes UB
}


prasoon@Prasoon:~/test_code$ cat ub.cpp
int main()
{ 
      int i=10;
      i += (i , i++, i) + i; // also invokes UB
}
prasoon@Prasoon:~/test_code$ g++ -Wsequence-point ub.cpp
prasoon@Prasoon:~/test_code$ 

I don't get any warning like 'operation on 'i' may be undefined.

Another similar example

int main()
{
    char *str;
    char array[100]= "Hello";
    if((str = array)[0] == 'H'){
         //do something
    }
}

As per my understanding (str = array)[0] also invokes UB but no warning is
given by g++ even after using that option.

Another example is 

int main()
{
   int a = 10;
   ++a = 100; // UB
}


                 reply	other threads:[~2012-01-12  9:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-51836-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).