public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "markus at trippelsdorf dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/55358] Valgrind errors
Date: Fri, 23 Nov 2012 13:10:00 -0000 [thread overview]
Message-ID: <bug-55358-4-h04qfyBr5e@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55358-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55358
--- Comment #5 from Markus Trippelsdorf <markus at trippelsdorf dot de> 2012-11-23 13:08:54 UTC ---
A new one:
==2442== Invalid write of size 8
==2442== at 0x672DF6: iterative_hash_canonical_type(tree_node*, unsigned
int) (gimple.c:3170)
==2442== by 0xD3F4A0: htab_find_slot (hashtab.c:712)
==2442== by 0x67DEA8: gimple_register_canonical_type(tree_node*)
(gimple.c:3438)
==2442== by 0x4D25C5: uniquify_nodes(data_in*, unsigned int) (lto.c:2050)
==2442== by 0x4D3A0A: lto_main() (lto.c:2089)
==2442== by 0x82195B: compile_file() (toplev.c:545)
==2442== by 0x8235CF: toplev_main(int, char**) (toplev.c:1881)
==2442== by 0x4ECD884: (below main) (libc-start.c:258)
==2442== Address 0x4031e98 is not stack'd, malloc'd or (recently) free'd
==2442==
next prev parent reply other threads:[~2012-11-23 13:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 18:57 [Bug other/55358] New: " hjl.tools at gmail dot com
2012-11-21 15:31 ` [Bug other/55358] " markus at trippelsdorf dot de
2012-11-21 16:53 ` markus at trippelsdorf dot de
2012-11-21 17:17 ` markus at trippelsdorf dot de
2012-11-21 17:20 ` jakub at gcc dot gnu.org
2012-11-23 13:10 ` markus at trippelsdorf dot de [this message]
2012-11-28 8:51 ` markus at trippelsdorf dot de
2012-11-28 13:21 ` markus at trippelsdorf dot de
2012-11-28 14:48 ` jakub at gcc dot gnu.org
2012-11-28 16:50 ` jakub at gcc dot gnu.org
2012-11-28 19:59 ` markus at trippelsdorf dot de
2013-10-14 9:24 ` rguenth 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-55358-4-h04qfyBr5e@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).