public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/63397] New: signed integer overflows in ira.c Date: Sun, 28 Sep 2014 09:55:00 -0000 [thread overview] Message-ID: <bug-63397-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63397 Bug ID: 63397 Summary: signed integer overflows in ira.c Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: trippels at gcc dot gnu.org CC: vmakarov at gcc dot gnu.org gcc build with -fsanitize=undefined shows: markus@x4 testsuite % gcc -c -Os gcc.dg/atomic/c11-atomic-exec-3.c gcc/ira.c:2465:24: runtime error: signed integer overflow: -2095982000 + -65536000 cannot be represented in type 'int' gcc/ira.c:2472:31: runtime error: signed integer overflow: -2095102000 + -65536000 cannot be represented in type 'int'
next reply other threads:[~2014-09-28 9:55 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-09-28 9:55 trippels at gcc dot gnu.org [this message] 2014-12-15 22:19 ` [Bug rtl-optimization/63397] " vmakarov at gcc dot gnu.org 2014-12-16 7:10 ` trippels 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-63397-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: 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).