public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/53706] [4.8 Regression] [ia64]: Bootstrap failure due to "Invalid write of size 8 at 0xBDC35E: variable_htab_free (var-tracking.c:1418)
Date: Sun, 17 Jun 2012 17:01:00 -0000 [thread overview]
Message-ID: <bug-53706-4-QiEgdgFRLs@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
Uros Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2012-06-17
CC| |aoliva at gcc dot gnu.org
Ever Confirmed|0 |1
--- Comment #3 from Uros Bizjak <ubizjak at gmail dot com> 2012-06-17 17:00:44 UTC ---
r188530 fails.
2012-06-13 Alexandre Oliva <aoliva@redhat.com>
PR debug/47624
* var-tracking.c (loc_exp_dep_pool): New.
(vt_emit_notes): Create and release the pool.
(compute_bb_dataflow): Use value-based locations in MO_VAL_SET.
(emit_notes_in_bb): Likewise.
(loc_exp_dep_insert): Deal with NOT_ONEPART vars.
(notify_dependents_of_changed_value): Likewise.
(notify_dependents_of_resolved_value): Check that NOT_ONEPART
variables don't have a VAR_LOC_DEP_LST.
(emit_note_insn_var_location): Expand NOT_ONEPART locs that are
VALUEs or MEMs of VALUEs.
next prev parent reply other threads:[~2012-06-17 17:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 12:40 [Bug rtl-optimization/53706] New: " 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 [this message]
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
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-QiEgdgFRLs@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).