public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sunfish at google dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/56956] ftrapv traps on valid abs-like code Date: Mon, 15 Apr 2013 05:12:00 -0000 [thread overview] Message-ID: <bug-56956-4-NjmLWQk2fm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56956-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56956 --- Comment #5 from Dan Gohman <sunfish at google dot com> 2013-04-15 05:12:30 UTC --- (In reply to comment #4) > (In reply to comment #2) > > (In reply to comment #1) > > > I think 'x' can not present negative value. > > > > The unary minus operator is defined for unsigned types. It doesn't produce > > signed overflow. > > According to C99 6.5.3.3 Point 3 and C99 6.5 Point 5: > > "The result of the unary '-' operator is the negative of its operand." > > "... if the result is ... not in the range of representable > values for its type... the behavior is undefined." > > So my understanding is that the evaluation expression '-x' is not > a representable value of 'uint64_t', which is undefined behavior, > resulting abort if -ftrav is issued. > > Perhaps my understanding is incorrect? :( Yes; unsigned types are an exception to the rule: C99 6.2.5p9 says "A computation involving unsigned operands can never overflow, because a result that cannot be represented by the resulting unsigned integer type is reduced modulo the number that is one greater than the largest value that can be represented by the resulting type." The wording is a little vague, but it means that negative results are converted to unsigned values by conceptually adding the maximum unsigned value plus one until the value is in range. >From gcc-bugs-return-420283-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Apr 15 05:14:31 2013 Return-Path: <gcc-bugs-return-420283-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 28111 invoked by alias); 15 Apr 2013 05:14:31 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 28085 invoked by uid 48); 15 Apr 2013 05:14:27 -0000 From: "sunfish at google dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/56956] ftrapv traps on valid abs-like code Date: Mon, 15 Apr 2013 05:14:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sunfish at google dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: <bug-56956-4-cc4NYyH3hH@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-56956-4@http.gcc.gnu.org/bugzilla/> References: <bug-56956-4@http.gcc.gnu.org/bugzilla/> X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 X-SW-Source: 2013-04/txt/msg01428.txt.bz2 Content-length: 491 http://gcc.gnu.org/bugzilla/show_bug.cgi?idV956 --- Comment #6 from Dan Gohman <sunfish at google dot com> 2013-04-15 05:14:27 UTC --- (In reply to comment #3) > Pulling the unary minus out into a separate statement, like this: > > uint64_t y = -x; > return x <= INT64_MAX ? x : -y; > > causes the program to execute correctly. Actually, I meant to write this: uint64_t y = -x; return x <= INT64_MAX ? x : y; and it still executes correctly, with no trap.
next prev parent reply other threads:[~2013-04-15 5:12 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-14 19:14 [Bug c/56956] New: " sunfish at google dot com 2013-04-15 0:58 ` [Bug c/56956] " jasonwucj at gmail dot com 2013-04-15 3:53 ` sunfish at google dot com 2013-04-15 3:54 ` sunfish at google dot com 2013-04-15 4:18 ` jasonwucj at gmail dot com 2013-04-15 5:12 ` sunfish at google dot com [this message] 2015-10-22 11:15 ` mpolacek at gcc dot gnu.org 2015-10-22 12:09 ` rguenth at gcc dot gnu.org 2015-10-28 11:20 ` [Bug middle-end/56956] " rguenth at gcc dot gnu.org 2015-10-29 8:22 ` rguenth at gcc dot gnu.org 2015-10-29 8:24 ` [Bug middle-end/56956] [4.9/5 Regression] " rguenth 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-56956-4-NjmLWQk2fm@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: linkBe 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).