public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/65316] [5 Regression] LTO: Uninitialized memory / ICE with -g -fno-lto-odr-type-merging: in types_same_for_odr, at ipa-devirt.c:465
Date: Fri, 06 Mar 2015 06:02:00 -0000 [thread overview]
Message-ID: <bug-65316-4-wSexVOncik@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65316-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65316
--- Comment #3 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
$ valgrind ./xgcc -B ./ -r -nostdlib -O2 -fno-lto-odr-type-merging -flto one.o
two.o
==98359== Memcheck, a memory error detector
==98359== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==98359== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==98359== Command: ./xgcc -B ./ -r -nostdlib -O2 -fno-lto-odr-type-merging
-flto one.o two.o
==98359==
==98359==
==98359== HEAP SUMMARY:
==98359== in use at exit: 153,577 bytes in 232 blocks
==98359== total heap usage: 365 allocs, 133 frees, 180,779 bytes allocated
==98359==
==98359== LEAK SUMMARY:
==98359== definitely lost: 36,072 bytes in 133 blocks
==98359== indirectly lost: 18 bytes in 1 blocks
==98359== possibly lost: 0 bytes in 0 blocks
==98359== still reachable: 117,487 bytes in 98 blocks
==98359== suppressed: 0 bytes in 0 blocks
==98359== Rerun with --leak-check=full to see details of leaked memory
==98359==
==98359== For counts of detected and suppressed errors, rerun with: -v
==98359== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 4)
and running
$ while true ; do ./xgcc -B ./ -r -nostdlib -O2 -fno-lto-odr-type-merging -flto
one.o two.o ; done
can you possibly valgrind it to figure out the source of uninitialized access?
next prev parent reply other threads:[~2015-03-06 6:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 18:54 [Bug lto/65316] New: " burnus at gcc dot gnu.org
2015-03-04 19:47 ` [Bug lto/65316] " trippels at gcc dot gnu.org
2015-03-05 0:01 ` hubicka at gcc dot gnu.org
2015-03-05 9:20 ` rguenth at gcc dot gnu.org
2015-03-06 6:02 ` hubicka at gcc dot gnu.org [this message]
2015-03-06 9:30 ` burnus at gcc dot gnu.org
2015-03-06 9:34 ` trippels at gcc dot gnu.org
2015-03-06 16:02 ` hubicka at gcc dot gnu.org
2015-03-06 18:25 ` hubicka at gcc dot gnu.org
2015-03-06 23:31 ` hubicka at ucw dot cz
2015-03-07 18:40 ` hubicka at gcc dot gnu.org
2015-03-07 20:34 ` hubicka at gcc dot gnu.org
2015-03-09 0:29 ` hubicka at gcc dot gnu.org
2015-03-09 1:40 ` hubicka 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-65316-4-wSexVOncik@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).