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 sanitizer/59503] New: Bogus integer-overflow error with long long with -m32
Date: Sat, 14 Dec 2013 00:57:00 -0000	[thread overview]
Message-ID: <bug-59503-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 59503
           Summary: Bogus integer-overflow error with long long with -m32
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: sanitizer
          Assignee: unassigned at gcc dot gnu.org
          Reporter: mpolacek at gcc dot gnu.org
                CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
                    jakub at gcc dot gnu.org, kcc at gcc dot gnu.org

We wrongly issue runtime error on:

int
main (void)
{
  long long int a = 14;
  long int b = 9;
  if ((a - b) != 5)
    __builtin_abort ();
  return 0;
}

$ gcc -O0 -fsanitize=signed-integer-overflow -m32 bug.c
$ ./a.out
bug.c:6:10: runtime error: signed integer overflow: 14 - 9 cannot be
represented in type 'long long int'
Aborted

This happens on PPC64 as well, as the bug is in generic handling of add/sub
instrumentation.


             reply	other threads:[~2013-12-14  0:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-14  0:57 mpolacek at gcc dot gnu.org [this message]
2013-12-14  0:58 ` [Bug sanitizer/59503] " mpolacek at gcc dot gnu.org
2013-12-14 12:20 ` mpolacek at gcc dot gnu.org
2013-12-14 12:20 ` 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-59503-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).