From: Pedro Alves <pedro@codesourcery.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, Daniel Jacobowitz <dan@codesourcery.com>
Subject: Re: [patch] STT_GNU_IFUNC support
Date: Wed, 17 Feb 2010 17:55:00 -0000 [thread overview]
Message-ID: <201002171755.10132.pedro@codesourcery.com> (raw)
In-Reply-To: <20100217173338.GA32328@host0.dyn.jankratochvil.net>
On Wednesday 17 February 2010 17:33:38, Jan Kratochvil wrote:
> > > What about making this GNU-IFUNC inferior call scheduling follow the "step"
> > > policy? Maybe the whole inferior calls should follow the "step" policy?
> >
> > Or "on", should be the same.
>
> Not so. I find "step" to be the reasonable default (and it has been so for
> a long time before me in RHEL/Fedora) and I find GNU-IFUNC resolving with
> locked scheduler also as a reasonable default. I do not find
> "scheduler-locking on" as a reasonable GDB default.
>
Oh, of course not. I was answering the first question,
about the specific infcall to resolve "strcmp" when the
user did "p strcmp" or "b strcmp". I assume you meant to
sched-lock that call, which would be the same as "on",
but maybe I misunderstood what you meant. A reply to
the second question would be similar to
the "That's another story." reply. ;-)
--
Pedro Alves
next prev parent reply other threads:[~2010-02-17 17:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-14 20:35 Jan Kratochvil
2010-02-14 21:43 ` Mark Kettenis
2010-02-14 21:59 ` Jan Kratochvil
2010-02-15 18:40 ` Daniel Jacobowitz
2010-02-15 18:49 ` Jan Kratochvil
2010-02-17 12:34 ` Pedro Alves
2010-02-17 14:19 ` Jan Kratochvil
2010-02-17 14:46 ` Daniel Jacobowitz
2010-02-17 17:45 ` Jan Kratochvil
2010-02-17 14:52 ` Pedro Alves
2010-02-17 17:33 ` Jan Kratochvil
2010-02-17 17:55 ` Pedro Alves [this message]
2010-02-17 18:12 ` Jan Kratochvil
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=201002171755.10132.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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