public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikulas at artax dot karlin.mff.cuni.cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/54848] New: -ftrapv doesn't work when assigning to an integer with smaller size
Date: Sun, 07 Oct 2012 16:13:00 -0000	[thread overview]
Message-ID: <bug-54848-4@http.gcc.gnu.org/bugzilla/> (raw)


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

             Bug #: 54848
           Summary: -ftrapv doesn't work when assigning to an integer with
                    smaller size
    Classification: Unclassified
           Product: gcc
           Version: 4.7.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: mikulas@artax.karlin.mff.cuni.cz
              Host: i686-pc-linux-gnu
            Target: i686-pc-linux-gnu
             Build: i686-pc-linux-gnu


When adding, subtracting or multiplying two integers and assigning the result
to a variable with smaller size, trap on overflow doesn't happen.

See for example this program:

#include <stdio.h>

int main(void)
{
        int a = 0x70000000;
        int b = 0x50000000;
        short c = a + b;
        printf("%x\n", c);
        return 0;
}

We compile the program without optimization and with -ftrapv, so that it should
crash because of integer overflow. But the program doesn't crash. If we replace
"short" with "int", an overflow crash happens correctly.


             reply	other threads:[~2012-10-07 16:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-07 16:13 mikulas at artax dot karlin.mff.cuni.cz [this message]
2012-10-08 10:44 ` [Bug middle-end/54848] " rguenth at gcc dot gnu.org
2024-05-20  0:24 ` bruno at clisp dot 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-54848-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).