From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Doug Evans'" <dje@google.com>
Cc: "'Hui Zhu'" <teawater@gmail.com>, <gdb-patches@sourceware.org>,
"'Pedro Alves'" <pedro@codesourcery.com>,
"'Stan Shebs'" <stan@codesourcery.com>,
"'Eli Zaretskii'" <eliz@gnu.org>, <tromey@redhat.com>,
"'Michael Snyder'" <msnyder@vmware.com>
Subject: RE: [RFA-new version][gdbserver] x86 agent expression bytecode compiler (speed up conditional tracepoints)
Date: Sun, 20 Jun 2010 17:02:00 -0000 [thread overview]
Message-ID: <003f01cb109a$4f5c2d00$ee148700$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <AANLkTikvzVRpbYYPaCtie_WasE8eUntZNCOxJw7IOPly@mail.gmail.com>
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Doug Evans
> Envoyé : Sunday, June 20, 2010 5:31 PM
> À : Pierre Muller
> Cc : Hui Zhu; gdb-patches@sourceware.org; Pedro Alves; Stan Shebs; Eli
> Zaretskii; tromey@redhat.com; Michael Snyder
> Objet : Re: [RFA-new version][gdbserver] x86 agent expression bytecode
> compiler (speed up conditional tracepoints)
>
> On Sun, Jun 20, 2010 at 2:29 AM, Pierre Muller
> <pierre.muller@ics-cnrs.unistra.fr> wrote:
> > As I said in a previous email, Ian's patch didn't work for me.
> > http://sourceware.org/ml/gdb-patches/2010-06/msg00424.html
>
> That's weird.
> Ian's approach involves removing the "if-always-true" test completely
> leaving just an asm.
> Can you send me the patch of Ian's that you tried?
I probably did a mistake indeed in my first try.
As it was not a patch to apply, I just modify the source directly,
and I suppose that I added the `do while (0)',
but forgot to remove the 'if (always_true ()) ' part, which would
explain why it works now and failed when I tried first...
Sorry about that false alarm...
Consider my RFA as withdrawn (see below),
but please it would be nice to get ASAP a patch in
that allows again to use the standard gdb_tester.sh script.
I cannot test any patch currently on gcc16 because gdbserver
compilation always fails.
> > I propose here another small patch that fixes the linking failure.
> > Using a volatile variable, it explicitly forbids the compiler
> > to optimize out code by forbidding the assumption that this value
> will
> > never change.
> >
> > This works on gcc16, an the approach seems reasonable.
>
> That's my patch. :-)
Sorry, I didn't read the whole thread, as I am not really interested in
this fast tracepoint feature.
> http://sourceware.org/ml/gdb-patches/2010-06/msg00374.html
Sorry for resubmitting a patch same as your, but
at least it is as if I voted for your patch too!
Pierre
next prev parent reply other threads:[~2010-06-20 17:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-07 16:00 [gdbserver] " Pedro Alves
2010-06-07 16:04 ` Michael Snyder
2010-06-07 16:35 ` Joel Brobecker
2010-06-10 17:28 ` Tom Tromey
2010-06-10 17:36 ` Pedro Alves
2010-06-10 18:43 ` Tom Tromey
2010-06-14 11:15 ` [NEWS/RFA] " Pedro Alves
2010-06-14 17:29 ` Eli Zaretskii
2010-06-14 22:19 ` Pedro Alves
2010-06-16 18:57 ` Doug Evans
2010-06-16 19:13 ` Stan Shebs
2010-06-16 19:16 ` Pedro Alves
2010-06-16 19:21 ` Doug Evans
2010-06-16 23:58 ` Ian Lance Taylor
2010-06-20 22:27 ` Pedro Alves
2010-06-16 19:31 ` Stan Shebs
2010-06-17 18:03 ` Michael Snyder
2010-06-19 16:13 ` Hui Zhu
2010-06-19 16:16 ` Doug Evans
2010-06-19 17:13 ` Hui Zhu
2010-06-19 17:26 ` Doug Evans
2010-06-20 9:30 ` [RFA-new version][gdbserver] " Pierre Muller
[not found] ` <-3945058798826177264@unknownmsgid>
2010-06-20 15:30 ` Doug Evans
2010-06-20 17:02 ` Pierre Muller [this message]
[not found] ` <-1673004315710326113@unknownmsgid>
2010-06-20 17:11 ` Doug Evans
2010-06-20 18:41 ` Tom Tromey
2010-06-20 20:36 ` Pierre Muller
2010-06-20 21:07 ` Pierre Muller
2010-06-21 1:47 ` Tom Tromey
2010-06-21 6:31 ` Pierre Muller
2010-06-20 18:31 ` [NEWS/RFA] Re: [gdbserver] " Tom Tromey
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='003f01cb109a$4f5c2d00$ee148700$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.com \
--cc=pedro@codesourcery.com \
--cc=stan@codesourcery.com \
--cc=teawater@gmail.com \
--cc=tromey@redhat.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