public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: fix for PR49888 var-tracking compile-time regression
Date: Fri, 18 Jan 2013 10:59:00 -0000	[thread overview]
Message-ID: <20130118105859.GB7269@tucnak.redhat.com> (raw)
In-Reply-To: <or4nif1qbb.fsf@livre.localdomain>

On Thu, Jan 17, 2013 at 06:56:40PM -0200, Alexandre Oliva wrote:
> From: Alexandre Oliva <aoliva@redhat.com>
> 
> for  gcc/ChangeLog
> 
> 	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.

Ok, thanks.

	Jakub

      reply	other threads:[~2013-01-18 10:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-16 10:29 Alexandre Oliva
2013-01-16 10:58 ` Jakub Jelinek
2013-01-16 13:25   ` Alexandre Oliva
2013-01-16 14:15     ` Jakub Jelinek
2013-01-16 16:55     ` Jakub Jelinek
2013-01-17 20:57       ` Alexandre Oliva
2013-01-18 10:59         ` Jakub Jelinek [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=20130118105859.GB7269@tucnak.redhat.com \
    --to=jakub@redhat.com \
    --cc=aoliva@redhat.com \
    --cc=gcc-patches@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).