public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/59755] New: BUG Increment Operator with Accessing Arrays
@ 2014-01-10 11:35 octo.nebula at gmail dot com
  2014-01-10 11:38 ` [Bug c/59755] " octo.nebula at gmail dot com
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: octo.nebula at gmail dot com @ 2014-01-10 11:35 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 59755
           Summary: BUG Increment Operator with Accessing Arrays
           Product: gcc
           Version: 4.8.2
            Status: UNCONFIRMED
          Severity: major
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: octo.nebula at gmail dot com

Guys,

The increment operator is not working right. The post ++ should increment value
of the index after the array expression. But in this case, it acts like the pre
++ version.

See code below:

#include <stdio.h>

int main()
{
    int A[2][2] = { { 5, 7}, {9, 10} };

    int m = 0, B[] = { 0, 0 };
    int C = 0, D = 0;

    C = A[m][B[m]];
    D = A[m][B[m++]];

    if  (C != D) {
      fprintf (stderr, "Error: C /= D\n");
      return 1;
    }

     return 0;
}


[sunny@localhost trash]$ gcc test.c
[sunny@localhost trash]$ ./a.out
Error: C /= D
[sunny@localhost trash]$ 


GCC version is 4.8.2


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug c/59755] BUG Increment Operator with Accessing Arrays
  2014-01-10 11:35 [Bug c/59755] New: BUG Increment Operator with Accessing Arrays octo.nebula at gmail dot com
@ 2014-01-10 11:38 ` octo.nebula at gmail dot com
  2014-01-10 13:15 ` octo.nebula at gmail dot com
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 5+ messages in thread
From: octo.nebula at gmail dot com @ 2014-01-10 11:38 UTC (permalink / raw)
  To: gcc-bugs

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

Arjun <octo.nebula at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |octo.nebula at gmail dot com

--- Comment #1 from Arjun <octo.nebula at gmail dot com> ---
In the example given above, C = 5 which is A[0][0] and D = 9 which is A[1][0].


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug c/59755] BUG Increment Operator with Accessing Arrays
  2014-01-10 11:35 [Bug c/59755] New: BUG Increment Operator with Accessing Arrays octo.nebula at gmail dot com
  2014-01-10 11:38 ` [Bug c/59755] " octo.nebula at gmail dot com
@ 2014-01-10 13:15 ` octo.nebula at gmail dot com
  2014-01-10 13:24 ` trippels at gcc dot gnu.org
  2014-01-10 13:26 ` mpolacek at gcc dot gnu.org
  3 siblings, 0 replies; 5+ messages in thread
From: octo.nebula at gmail dot com @ 2014-01-10 13:15 UTC (permalink / raw)
  To: gcc-bugs

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

Arjun <octo.nebula at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|INVALID                     |WONTFIX

--- Comment #3 from Arjun <octo.nebula at gmail dot com> ---
Why is that so?

Shouldn't the value of m increment after the array indexing? Could you please
explain?


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug c/59755] BUG Increment Operator with Accessing Arrays
  2014-01-10 11:35 [Bug c/59755] New: BUG Increment Operator with Accessing Arrays octo.nebula at gmail dot com
  2014-01-10 11:38 ` [Bug c/59755] " octo.nebula at gmail dot com
  2014-01-10 13:15 ` octo.nebula at gmail dot com
@ 2014-01-10 13:24 ` trippels at gcc dot gnu.org
  2014-01-10 13:26 ` mpolacek at gcc dot gnu.org
  3 siblings, 0 replies; 5+ messages in thread
From: trippels at gcc dot gnu.org @ 2014-01-10 13:24 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #4 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
Please read the section on -Wsequence-point:
http://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug c/59755] BUG Increment Operator with Accessing Arrays
  2014-01-10 11:35 [Bug c/59755] New: BUG Increment Operator with Accessing Arrays octo.nebula at gmail dot com
                   ` (2 preceding siblings ...)
  2014-01-10 13:24 ` trippels at gcc dot gnu.org
@ 2014-01-10 13:26 ` mpolacek at gcc dot gnu.org
  3 siblings, 0 replies; 5+ messages in thread
From: mpolacek at gcc dot gnu.org @ 2014-01-10 13:26 UTC (permalink / raw)
  To: gcc-bugs

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

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mpolacek at gcc dot gnu.org
         Resolution|WONTFIX                     |INVALID


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2014-01-10 13:26 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-01-10 11:35 [Bug c/59755] New: BUG Increment Operator with Accessing Arrays octo.nebula at gmail dot com
2014-01-10 11:38 ` [Bug c/59755] " octo.nebula at gmail dot com
2014-01-10 13:15 ` octo.nebula at gmail dot com
2014-01-10 13:24 ` trippels at gcc dot gnu.org
2014-01-10 13:26 ` mpolacek at gcc dot gnu.org

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