public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/67649] New: trunk build with valgrind fail in get_def_blocks_for
Date: Sun, 20 Sep 2015 15:12:00 -0000 [thread overview]
Message-ID: <bug-67649-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67649
Bug ID: 67649
Summary: trunk build with valgrind fail in get_def_blocks_for
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: dcb314 at hotmail dot com
Target Milestone: ---
I just tried to build gcc trunk of today (20150920) on x86_64
and got this:
/home/dcb/gcc/working/./gcc/xgcc -B/home/dcb/gcc/working/./gcc/
-B/home/dcb/gcc/results/x86_64-pc-linux-gnu/bin/
-B/home/dcb/gcc/results/x86_64-pc-linux-gnu/lib/ -isystem
/home/dcb/gcc/results/x86_64-pc-linux-gnu/include -isystem
/home/dcb/gcc/results/x86_64-pc-linux-gnu/sys-include -g -O3 -march=native
-O2 -g -O3 -march=native -DIN_GCC -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition
-isystem ./include -fpic -mlong-double-80 -DUSE_ELF_SYMVER -g -DIN_LIBGCC2
-fbuilding-libgcc -fno-stack-protector -fpic -mlong-double-80
-DUSE_ELF_SYMVER -I. -I. -I../.././gcc -I../../../src/trunk/libgcc
-I../../../src/trunk/libgcc/. -I../../../src/trunk/libgcc/../gcc
-I../../../src/trunk/libgcc/../include
-I../../../src/trunk/libgcc/config/libbid -DENABLE_DECIMAL_BID_FORMAT
-DHAVE_CC_TLS -DUSE_TLS -o _ashldi3.o -MT _ashldi3.o -MD -MP -MF _ashldi3.dep
-DL_ashldi3 -c ../../../src/trunk/libgcc/libgcc2.c -fvisibility=hidden
-DHIDE_EXPORTS
==9820== Invalid write of size 8
==9820== at 0x670401: bitmap_initialize_stat (bitmap.h:332)
==9820== by 0x670401: bitmap_obstack_alloc_stat(bitmap_obstack*)
(bitmap.c:286)
==9820== by 0xAEB9B3: get_def_blocks_for (tree-into-ssa.c:489)
==9820== by 0xAEB9B3: set_livein_block (tree-into-ssa.c:543)
next reply other threads:[~2015-09-20 15:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-20 15:12 dcb314 at hotmail dot com [this message]
2015-09-21 7:41 ` [Bug middle-end/67649] " rguenth at gcc dot gnu.org
2015-09-21 8:44 ` dcb314 at hotmail dot com
2015-09-21 9:28 ` trippels at gcc dot gnu.org
2015-09-21 9:33 ` trippels at gcc dot gnu.org
2015-09-21 9:35 ` trippels at gcc dot gnu.org
2015-09-21 10:42 ` trippels at gcc dot gnu.org
2015-09-21 11:20 ` trippels at gcc dot gnu.org
2015-09-22 2:39 ` miyuki at gcc dot gnu.org
2015-09-22 2:42 ` miyuki at gcc dot gnu.org
2015-09-22 6:41 ` trippels at gcc dot gnu.org
2015-09-23 2:31 ` miyuki at gcc dot gnu.org
2015-09-23 2:41 ` miyuki 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-67649-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).