From: Tom Tromey <tromey@redhat.com>
To: Hui Zhu <teawater@gmail.com>
Cc: linux-kernel@vger.kernel.org, Michael Snyder <msnyder@vmware.com>,
Marc Khouzam <marc.khouzam@ericsson.com>,
Thiago Jung Bauermann <thiago.bauermann@gmail.com>,
Steven <mqyoung@gmail.com>,
colyli@gmail.com, Christoph Hellwig <hch@infradead.org>,
"gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: [PATCH] Linux Kernel GDB tracepoint module 2011-02-05
Date: Tue, 08 Feb 2011 09:00:47 -0700 [thread overview]
Message-ID: <m3y65qv7m8.fsf@fleche.redhat.com> (raw)
In-Reply-To: <AANLkTinMx8mJYiDps3TuuaA1B4NLHi-PuCKm2=sTqyR0@mail.gmail.com> (Hui Zhu's message of "Tue, 8 Feb 2011 21:23:52 +0800")
>>>>> ">" == Hui Zhu <teawater@gmail.com> writes:
>> My gcc is 4.4.5. Does it have VTA?
Nope. VTA went in for 4.5.
>> Use the patch is easier than update gcc sometimes, right? :)
Yeah.
>> BTW does VTA can handle the issue that after -O2 a lot of code
>> execution order is worong?
>> It affect me when I debug the Linux Kernel in qemu.
My understanding is that VTA is solely about better tracking of values
through optimization passes. It doesn't affect code reordering, by
design.
Tom
next prev parent reply other threads:[~2011-02-08 16:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTikhfhYjvmvXtjW-Mszpq8d_3Syo=H4zqWe+1hEg__12255.0142732964$1296923928$gmane$org@mail.gmail.com>
2011-02-07 16:25 ` [PATCH] Linux Kernel GDB tracepoint module 2011-02-05 Tom Tromey
2011-02-08 13:23 ` Hui Zhu
2011-02-08 16:00 ` Tom Tromey [this message]
2011-02-09 13:25 ` Hui Zhu
2011-02-11 16:29 ` Tom Tromey
2011-02-23 5:32 ` Hui Zhu
2011-02-08 16:27 ` Jan Kratochvil
2011-02-05 16:37 Hui Zhu
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=m3y65qv7m8.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=colyli@gmail.com \
--cc=gdb@sourceware.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.khouzam@ericsson.com \
--cc=mqyoung@gmail.com \
--cc=msnyder@vmware.com \
--cc=teawater@gmail.com \
--cc=thiago.bauermann@gmail.com \
/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