public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/58712] [4.9 Regression] issues found by --enable-checking=valgrind
Date: Mon, 14 Oct 2013 08:37:00 -0000 [thread overview]
Message-ID: <bug-58712-4-RxuUvY2Ce3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58712-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58712
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Markus Trippelsdorf from comment #0)
> 3)
> ==1269== Invalid write of size 8
> ==1269== at 0x63BDBD: iterative_hash_canonical_type(tree_node*, unsigned
> int) (gimple.c:3220)
> ==1269== by 0xC224F1: htab_find_slot (hashtab.c:704)
> ==1269== by 0x641818: gimple_register_canonical_type(tree_node*)
> (gimple.c:3488)
> ==1269== by 0x504AEB: lto_read_decls(lto_file_decl_data*, void const*,
> vec<ld_plugin_symbol_resolution, va_heap, vl_ptr>) (lto.c:2495)
> ==1269== by 0x505CBB: lto_main() (lto.c:2786)
> ==1269== by 0x7B3A95: compile_file() (toplev.c:546)
> ==1269== by 0x7B5619: toplev_main(int, char**) (toplev.c:1893)
> ==1269== by 0x4ED5A6D: (below main) (in /lib64/libc-2.18.90.so)
> ==1269== Address 0x40325a0 is not stack'd, malloc'd or (recently) free'd
>
> This is an older issue, see PR55358 for more info.
By inspection I have created a patch and am bootstrapping/testing it for this
issue.
next prev parent reply other threads:[~2013-10-14 8:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-13 12:14 [Bug other/58712] New: " markus at trippelsdorf dot de
2013-10-14 7:36 ` [Bug other/58712] " markus at trippelsdorf dot de
2013-10-14 8:37 ` rguenth at gcc dot gnu.org [this message]
2013-10-14 9:01 ` rguenth at gcc dot gnu.org
2013-10-14 9:24 ` rguenth at gcc dot gnu.org
2013-10-15 7:15 ` markus at trippelsdorf dot de
2013-10-24 17:28 ` law at gcc dot gnu.org
2013-11-05 15:02 ` rguenth at gcc dot gnu.org
2013-11-05 15:12 ` octoploid at yandex dot com
2013-11-05 15:15 ` rguenth at gcc dot gnu.org
2013-11-10 11:14 ` octoploid at yandex dot com
2013-11-12 21:33 ` vmakarov at gcc dot gnu.org
2013-11-24 9:52 ` octoploid at yandex dot com
2014-01-15 8:08 ` jakub at gcc dot gnu.org
2014-01-16 8:36 ` trippels at gcc dot gnu.org
2014-01-29 10:35 ` jakub at gcc dot gnu.org
2014-02-04 12:20 ` jakub at gcc dot gnu.org
2014-02-04 12:32 ` jakub 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-58712-4-RxuUvY2Ce3@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).