This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 2/3] skip_prolgoue (amd64)
- From: Doug Evans <dje at google dot com>
- To: Yao Qi <yao at codesourcery dot com>
- Cc: Pedro Alves <palves at redhat dot com>, Mark Kettenis <mark dot kettenis at xs4all dot nl>, gdb-patches <gdb-patches at sourceware dot org>
- Date: Wed, 4 Dec 2013 09:42:04 -0800
- Subject: Re: [PATCH 2/3] skip_prolgoue (amd64)
- Authentication-results: sourceware.org; auth=none
- References: <1385735051-27558-1-git-send-email-yao at codesourcery dot com> <1385735051-27558-3-git-send-email-yao at codesourcery dot com> <201311291436 dot rATEaZ5Z030292 at glazunov dot sibelius dot xs4all dot nl> <201311291605 dot rATG5XVb030184 at glazunov dot sibelius dot xs4all dot nl> <52994E79 dot 4000004 at codesourcery dot com> <5299B9D0 dot 2020304 at redhat dot com> <529C37A2 dot 9000207 at codesourcery dot com>
On Sun, Dec 1, 2013 at 11:32 PM, Yao Qi <yao@codesourcery.com> wrote:
> GDB target cache contains both code cache and stack cache.
I hate to keep harping on this, but there's been confusion before and
I want to avoid it in the future.
There is no such thing as the "code cache" or "stack cache".
There is just the target cache that caches target memory.
I can turn off the code cache optimization and stack cache
optimization, and still populate the cache with data from .text or
.data or .stack (so to speak) or whatever.