[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] extra read after write
|
Hi,
is there a big performance hit to do that extra read after
the write? I'm curious why you would want to make it
conditional?
I'm not sure why the memory is re-read, but my guess is
that it is to make sure we display what is really in the
target.
Since we use GDB, it is safer to ask GDB what is in memory
than to assume the memory write did exactly what
we expected. This has been the approach in most of
the code, where we rely on GDB for the majority of the
knowledge
shown to the user.
Marc
Hi All,
In MemoryView when we try to edit the value in memory
view, it first tries to write memory and then upon success it reads from
memory(class : MIMemory and function: setMemory ) and displays updated values
in the user interface.
Why is an extra read after write required ?
Data is already written into memory, so we can create the memory block
and update the memory cache. Will it cause any problems if this approach is
followed.
we are planning to conditionalize extra read after write
based on the preference, will it be useful for CDT ?
Thanks
Harish Dewan
Tensilica India
