This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Multiplexed registers and invalidating the register cache

From: Orjan Friberg <orjan dot friberg at axis dot com>
To: Daniel Jacobowitz <drow at false dot org>
Cc: gdb-patches at sources dot redhat dot com
Date: Thu, 15 Apr 2004 13:24:45 +0200
Subject: Re: Multiplexed registers and invalidating the register cache
Organization: Axis Communications
References: <407D242B.109@axis.com> <20040414144607.GA5700@nevyn.them.org> <407E67EA.80701@axis.com>

Orjan Friberg wrote:

Daniel Jacobowitz wrote:
I think you should make this change unconditionally - and flush the
entire frame cache.
Pardon my ignorance, but why should the entire frame cache be flushed, instead of just invalidating the current set of registers? Is it because frame pointer/return address registers (or something else affecting other frames) might change?

Too quick on the send button... just found the flushregs command, which does what I want for the time being (flushing the register cache).

--
Orjan Friberg
Axis Communications

Follow-Ups:
- Re: Multiplexed registers and invalidating the register cache
  - From: Andrew Cagney

References:
- Multiplexed registers and invalidating the register cache
  - From: Orjan Friberg
- Re: Multiplexed registers and invalidating the register cache
  - From: Daniel Jacobowitz
- Re: Multiplexed registers and invalidating the register cache
  - From: Orjan Friberg

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]