public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zhongyunde at huawei dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/101119] New: Missing the check about modify global variable for __attribute__((const)) function
Date: Fri, 18 Jun 2021 10:56:15 +0000	[thread overview]
Message-ID: <bug-101119-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 101119
           Summary: Missing the check about modify global variable for
                    __attribute__((const)) function
           Product: gcc
           Version: 10.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: zhongyunde at huawei dot com
  Target Milestone: ---

As __attribute__((const)) function should have no side effect, so it won't
modify any global variable. but with the newest gcc, it doesn't do such check.


test base on the ARM64 gcc 11.1 on https://gcc.godbolt.org/ with option -O3 -S
-fno-inline -g0 -Wall -Werror.

=====================================================
#include <stdio.h>
int gValue = 1;
class NPair /*: protected Pointers */ {
public:
  int bins[10];
  //int exclusion(int n) __attribute__((const));
  __attribute__((const)) int exclusion (int n) const {
    printf ("before %d\n", bins[0]);
    NPair* pt = const_cast<NPair*>(this);
    pt->bins[0] = 1;
    printf ("after %d\n", bins[0]);
    return gValue++; // expect a error
  }
  NPair (void) {
     bins[0] = 3;
  }
};

// extern int * __restrict bins;
class NPair nPair;

int main (void)
{
  int tmp = nPair.bins[0];

  (void)nPair.exclusion(1);

  return tmp == nPair.bins[0];
}

             reply	other threads:[~2021-06-18 10:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-18 10:56 zhongyunde at huawei dot com [this message]
2021-06-18 12:37 ` [Bug c++/101119] " rguenth at gcc dot gnu.org
2021-06-18 17:05 ` 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-101119-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).