public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zeccav at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/61657] Undefined behavior in loop-iv.c Date: Fri, 21 Aug 2015 13:43:00 -0000 [thread overview] Message-ID: <bug-61657-4-qLEVava2d6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61657-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61657 --- Comment #8 from Vittorio Zecca <zeccav at gmail dot com> --- Maybe the easiest way to reproduce the issue is as in the following; gdb ~/local/gcc-5.2.0-sanitized/libexec/gcc/x86_64-unknown-linux-gnu/5.2.0/cc1 GNU gdb (GDB) Fedora 7.8.2-39.fc21 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /home/vitti/local/gcc-5.2.0-sanitized/libexec/gcc/x86_64-unknown-linux-gnu/5.2.0/cc1...done. (gdb) break ../../gcc-5.2.0/gcc/loop-iv.c:2671 Breakpoint 1 at 0x153209e: file ../../gcc-5.2.0/gcc/loop-iv.c, line 2671. (gdb) run gccerr14.c -O -quiet -funroll-loops Starting program: /home/vitti/local/gcc-5.2.0-sanitized/libexec/gcc/x86_64-unknown-linux-gnu/5.2.0/cc1 gccerr14.c -O -quiet -funroll-loops Missing separate debuginfos, use: debuginfo-install glibc-2.20-8.fc21.x86_64 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Breakpoint 1, iv_number_of_iterations (loop=0x2aaab633f360, insn=0x2aaab635e400, condition=0x2aaab6362d98, desc=0x7fffffffa810) at ../../gcc-5.2.0/gcc/loop-iv.c:2671 2671 max = (uint64_t) (up - down) / inc + 1; Missing separate debuginfos, use: debuginfo-install gmp-6.0.0-9.fc21.x86_64 libmpc-1.0.2-3.fc21.x86_64 mpfr-3.1.2-8.fc21.x86_64 (gdb) print up $1 = 7 (gdb) print down $2 = -9223372036854775808 But you need an unoptimized version of cc1
next prev parent reply other threads:[~2015-08-21 13:43 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-30 11:29 [Bug rtl-optimization/61657] New: " jakub at gcc dot gnu.org 2014-09-28 9:07 ` [Bug rtl-optimization/61657] " trippels at gcc dot gnu.org 2014-09-28 9:09 ` trippels at gcc dot gnu.org 2014-09-28 9:09 ` trippels at gcc dot gnu.org 2015-07-21 18:44 ` zeccav at gmail dot com 2015-07-21 19:13 ` zeccav at gmail dot com 2015-08-21 11:17 ` zeccav at gmail dot com 2015-08-21 11:22 ` trippels at gcc dot gnu.org 2015-08-21 13:43 ` zeccav at gmail dot com [this message] 2015-08-21 13:51 ` trippels at gcc dot gnu.org 2015-08-21 16:45 ` trippels at gcc dot gnu.org 2015-08-21 16:51 ` 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-61657-4-qLEVava2d6@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).