public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/65830] New: -Wno-shift-count-negative -Wno-shift-count-overflow don't work with const ints
Date: Tue, 21 Apr 2015 13:02:00 -0000	[thread overview]
Message-ID: <bug-65830-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 65830
           Summary: -Wno-shift-count-negative -Wno-shift-count-overflow
                    don't work with const ints
           Product: gcc
           Version: 6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: mpolacek at gcc dot gnu.org

When dealing with const ints, the warning can't be suppressed with
-Wno-shift-count-negative -Wno-shift-count-overflow.

A c-c++-common/ test case:

/* PR c/... */
/* { dg-do compile } */
/* { dg-options "-O -Wno-shift-count-negative -Wno-shift-count-overflow" } */

int
foo (int x)
{
  const int a = sizeof (int) * __CHAR_BIT__;
  const int b = -7;
  int c = 0;
  c += x << a;    /* { dg-bogus "left shift count >= width of type" } */
  c += x << b;    /* { dg-bogus "left shift count is negative" } */
  c += x >> a;    /* { dg-bogus "right shift count >= width of type" } */
  c += x >> b;  /* { dg-bogus "right shift count is negative" } */
  return c;
}


             reply	other threads:[~2015-04-21 13:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-21 13:02 mpolacek at gcc dot gnu.org [this message]
2015-04-21 13:03 ` [Bug c/65830] " mpolacek at gcc dot gnu.org
2015-04-24 11:54 ` mpolacek at gcc dot gnu.org
2015-04-24 11:54 ` mpolacek 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-65830-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).