public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aoliva at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/53706] [4.8 Regression] Bootstrap failure due to "Invalid write of size 8 at 0xBDC35E: variable_htab_free (var-tracking.c:1418)
Date: Wed, 27 Jun 2012 02:00:00 -0000 [thread overview]
Message-ID: <bug-53706-4-3gWuEn9fzg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53706-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53706
Alexandre Oliva <aoliva at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #17 from Alexandre Oliva <aoliva at gcc dot gnu.org> 2012-06-27 01:59:22 UTC ---
Rainer, I pretty sure Uros' revised patch in comment 10 should fix the problem.
We shouldn't release th pool before we destroy the dataflow sets, because they
will access and release backrefs that may be in the pool.
Uros, you reported it ddn't bootstrap, bu you didn't provide any details. Are
you sure it wasn't for some unrelated reason?
I'll momentarily test a variant of that patch on ia64, but I don't see why it
would fare any different.
next prev parent reply other threads:[~2012-06-27 2:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 12:40 [Bug rtl-optimization/53706] New: [4.8 Regression] [ia64]: " ubizjak at gmail dot com
2012-06-17 12:42 ` [Bug rtl-optimization/53706] " ubizjak at gmail dot com
2012-06-17 16:49 ` ubizjak at gmail dot com
2012-06-17 17:01 ` ubizjak at gmail dot com
2012-06-17 21:59 ` hjl.tools at gmail dot com
2012-06-17 22:01 ` hjl.tools at gmail dot com
2012-06-18 7:51 ` [Bug rtl-optimization/53706] [4.8 Regression] " jakub at gcc dot gnu.org
2012-06-18 9:50 ` aoliva at gcc dot gnu.org
2012-06-21 6:56 ` ubizjak at gmail dot com
2012-06-21 6:59 ` ubizjak at gmail dot com
2012-06-21 7:34 ` ubizjak at gmail dot com
2012-06-21 13:19 ` uweigand at gcc dot gnu.org
2012-06-21 15:24 ` ubizjak at gmail dot com
2012-06-25 14:56 ` ro at gcc dot gnu.org
2012-06-25 15:17 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-06-26 16:28 ` wschmidt at gcc dot gnu.org
2012-06-26 20:31 ` aoliva at gcc dot gnu.org
2012-06-27 2:00 ` aoliva at gcc dot gnu.org [this message]
2012-06-27 5:45 ` aoliva at gcc dot gnu.org
2012-06-27 6:31 ` aoliva at gcc dot gnu.org
2012-06-27 9:02 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-06-27 20:10 ` hp at gcc dot gnu.org
2012-06-28 7:47 ` aoliva at gcc dot gnu.org
2012-07-01 11:00 ` dcb314 at hotmail dot com
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-53706-4-3gWuEn9fzg@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).