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 other/63426] [meta-bug] Issues found with -fsanitize=undefined Date: Wed, 01 Oct 2014 11:13:00 -0000 [thread overview] Message-ID: <bug-63426-4-sJoq1CpfhE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63426-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63426 --- Comment #1 from Markus Trippelsdorf <trippels at gcc dot gnu.org> --- Here's the full list (cut down to one instance per issue) of todays trunk: gcc/fortran/interface.c:2667:43: runtime error: load of value 1818451807, which is not a valid value for type 'expr_t' gcc/fortran/interface.c:2908:47: runtime error: load of value 108398592, which is not a valid value for type 'ar_type' gcc/fortran/trans-array.c:2211:9: runtime error: load of value 92, which is not a valid value for type 'bool' gcc/fortran/trans-expr.c:2286:48: runtime error: negation of -9223372036854775808 cannot be represented in type 'long int'; cast to an unsigned type to negate this value to itself gcc/hwint.h:250:29: runtime error: shift exponent 64 is too large for 64-bit type 'long int' gcc/ira.c:2465:24: runtime error: signed integer overflow: -2097715000 + -65536000 cannot be represented in type 'int' gcc/ira.c:2472:31: runtime error: signed integer overflow: -2097600000 + -65536000 cannot be represented in type 'int' gcc/loop-iv.c:2305:24: runtime error: signed integer overflow: 9223372036854775807 - -9223372036854775808 cannot be represented in type 'long int' gcc/loop-iv.c:2643:14: runtime error: signed integer overflow: 9223372036854775806 - -9223372036854775808 cannot be represented in type 'long int' gcc/tree-data-ref.c:2352:38: runtime error: signed integer overflow: 1073741824 + 1073741824 cannot be represented in type 'int' gcc/tree-data-ref.c:2443:16: runtime error: negation of -2147483648 cannot be represented in type 'int'; cast to an unsigned type to negate this value to itself gcc/tree-ssa-loop-ivopts.c:4192:24: runtime error: signed integer overflow: 4 * 4611686018427387903 cannot be represented in type 'long int' libiberty/cp-demangle.c:4074:40: runtime error: variable length array bound evaluates to non-positive value 0 libiberty/cp-demangle.c:4075:43: runtime error: variable length array bound evaluates to non-positive value 0 There are also a couple of buggy testcases: testsuite/gcc.dg/compat/generate-random_r.c:363:19: runtime error: signed integer overflow: 1627687941 + 1735697613 cannot be represented in type 'int' testsuite/gcc.dg/compat/struct-layout-1_generate.c:1081:13: runtime error: shift exponent 64 is too large for 64-bit type 'long long unsigned int' testsuite/g++.dg/compat/../../gcc.dg/compat/generate-random_r.c:363:19: runtime error: signed integer overflow: 1627687941 + 1735697613 cannot be represented in type 'int' testsuite/g++.dg/compat/struct-layout-1_generate.c:795:26: runtime error: shift exponent 64 is too large for 64-bit type 'long long unsigned int' testsuite/g++.dg/compat/struct-layout-1_generate.c:805:13: runtime error: shift exponent 65 is too large for 64-bit type 'long long unsigned int
next prev parent reply other threads:[~2014-10-01 11:13 UTC|newest] Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-10-01 9:17 [Bug other/63426] New: " trippels at gcc dot gnu.org 2014-10-01 9:55 ` [Bug other/63426] " mpolacek at gcc dot gnu.org 2014-10-01 11:13 ` trippels at gcc dot gnu.org [this message] 2014-10-28 14:09 ` trippels at gcc dot gnu.org 2014-11-19 12:21 ` trippels at gcc dot gnu.org 2014-11-20 10:24 ` trippels at gcc dot gnu.org 2014-12-16 7:10 ` trippels at gcc dot gnu.org 2015-03-03 9:16 ` trippels at gcc dot gnu.org 2015-03-04 17:33 ` trippels at gcc dot gnu.org 2015-04-22 12:01 ` jakub at gcc dot gnu.org 2015-07-16 9:15 ` rguenth at gcc dot gnu.org 2015-08-21 16:51 ` trippels at gcc dot gnu.org 2015-08-23 5:22 ` zeccav at gmail dot com 2020-06-06 1:54 ` aoliva at gcc dot gnu.org 2020-10-13 15:08 ` aldyh at gcc dot gnu.org 2021-01-04 9:08 ` pault at gcc dot gnu.org 2021-01-04 11:14 ` rguenth at gcc dot gnu.org 2021-01-13 13:35 ` nathan at gcc dot gnu.org 2021-01-19 19:38 ` nathan at gcc dot gnu.org 2021-01-21 8:58 ` marxin at gcc dot gnu.org 2021-01-21 13:07 ` nathan at gcc dot gnu.org 2021-01-21 18:42 ` nathan at gcc dot gnu.org 2021-02-23 10:16 ` marxin at gcc dot gnu.org 2021-02-27 9:34 ` zeccav at gmail dot com 2021-03-05 11:56 ` ebotcazou at gcc dot gnu.org 2021-04-29 10:57 ` rearnsha at gcc dot gnu.org 2021-08-27 18:49 ` jakub at gcc dot gnu.org 2021-09-01 8:21 ` pinskia at gcc dot gnu.org 2021-10-12 8:49 ` burnus at gcc dot gnu.org 2021-11-05 22:26 ` hubicka at gcc dot gnu.org 2021-11-12 14:08 ` marxin at gcc dot gnu.org 2021-11-14 13:15 ` aldyh at gcc dot gnu.org 2021-11-19 11:34 ` marxin at gcc dot gnu.org 2021-11-27 12:03 ` jakub at gcc dot gnu.org 2021-12-25 14:57 ` fxcoudert at gcc dot gnu.org 2022-01-17 15:16 ` rguenth at gcc dot gnu.org 2022-01-18 9:29 ` rguenth at gcc dot gnu.org 2022-03-09 3:22 ` xry111 at mengyan1223 dot wang 2022-03-09 9:28 ` xry111 at mengyan1223 dot wang 2022-03-23 18:13 ` anlauf at gcc dot gnu.org 2022-03-28 7:53 ` jakub at gcc dot gnu.org 2022-06-30 2:03 ` xry111 at gcc dot gnu.org 2023-05-17 8:44 ` jamborm at gcc dot gnu.org 2023-06-13 9:16 ` jamborm at gcc dot gnu.org 2023-07-10 20:46 ` xry111 at gcc dot gnu.org 2023-08-15 15:19 ` jamborm at gcc dot gnu.org 2024-01-25 19:59 ` pinskia at gcc dot gnu.org 2024-01-26 5:03 ` pinskia at gcc dot gnu.org 2024-03-08 8:29 ` jakub at gcc dot gnu.org 2024-03-22 14:01 ` law 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-63426-4-sJoq1CpfhE@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).