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 debug/49888] VTA: -O2 -g variable value changes, it does not change in the source Date: Fri, 18 Jan 2013 11:01:00 -0000 [thread overview] Message-ID: <bug-49888-4-iefElm4rjy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49888-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49888 --- Comment #14 from Alexandre Oliva <aoliva at gcc dot gnu.org> 2013-01-18 10:58:45 UTC --- Author: aoliva Date: Fri Jan 18 10:58:15 2013 New Revision: 195291 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=195291 Log: PR debug/54114 PR debug/54402 PR debug/49888 * var-tracking.c (negative_power_of_two_p): New. (global_get_addr_cache, local_get_addr_cache): New. (get_addr_from_global_cache, get_addr_from_local_cache): New. (vt_canonicalize_addr): Rewrite using the above. Adjust the heading comment. (vt_stack_offset_p): Remove. (vt_canon_true_dep): Always canonicalize loc's address. (clobber_overlapping_mems): Make sure we have a MEM. (local_get_addr_clear_given_value): New. (val_reset): Clear local cached entries. (compute_bb_dataflow): Create and release the local cache. Disable duplicate MEMs clobbering. (emit_notes_in_bb): Clobber MEMs likewise. (vt_emit_notes): Create and release the local cache. (vt_initialize, vt_finalize): Create and release the global cache, respectively. * alias.c (rtx_equal_for_memref_p): Compare operands of ENTRY_VALUEs. Modified: trunk/gcc/ChangeLog trunk/gcc/alias.c trunk/gcc/var-tracking.c
prev parent reply other threads:[~2013-01-18 11:00 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-07-28 18:04 [Bug debug/49888] New: " jan.kratochvil at redhat dot com 2012-05-23 9:36 ` [Bug debug/49888] " aoliva at gcc dot gnu.org 2012-06-13 21:44 ` aoliva at gcc dot gnu.org 2012-06-13 21:58 ` aoliva at gcc dot gnu.org 2012-06-13 22:10 ` jan.kratochvil at redhat dot com 2012-06-22 1:31 ` aoliva at gcc dot gnu.org 2012-06-22 1:34 ` aoliva at gcc dot gnu.org 2012-06-28 7:41 ` aoliva at gcc dot gnu.org 2012-07-06 11:37 ` aoliva at gcc dot gnu.org 2012-11-08 2:57 ` aoliva at gcc dot gnu.org 2013-01-16 4:32 ` aoliva at gcc dot gnu.org 2013-01-18 10:59 ` aoliva at gcc dot gnu.org 2013-01-18 11:01 ` aoliva at gcc dot gnu.org [this message]
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-49888-4-iefElm4rjy@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: linkBe 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).