From: "Frank Ch. Eigler" <fche@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Vara Prasad <prasadav@us.ibm.com>,
"Frank Ch. Eigler" <fche@redhat.com>,
Ingo Molnar <mingo@elte.hu>,
Paul Mundt <lethal@linux-sh.org>,
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
linux-kernel <linux-kernel@vger.kernel.org>,
Jes Sorensen <jes@sgi.com>, Andrew Morton <akpm@osdl.org>,
Tom Zanussi <zanussi@us.ibm.com>,
Richard J Moore <richardj_moore@uk.ibm.com>,
Michel Dagenais <michel.dagenais@polymtl.ca>,
Christoph Hellwig <hch@infradead.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
William Cohen <wcohen@redhat.com>,
"Martin J. Bligh" <mbligh@mbligh.org>,
systemtap <systemtap@sourceware.org>
Subject: Re: tracepoint maintainance models
Date: Mon, 18 Sep 2006 19:40:00 -0000 [thread overview]
Message-ID: <20060918193952.GR3951@redhat.com> (raw)
In-Reply-To: <1158608981.6069.167.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 617 bytes --]
Hi -
On Mon, Sep 18, 2006 at 08:49:40PM +0100, Alan Cox wrote:
> [...]
> Then what we really need by the sound of it is enough gcc smarts to do
> something of the form [...]
> .section "debugbits"
> [...]
> Can gcc do any of that for us today ?
This is not that different from what gcc does for DWARF. Trouble is,
there appear to exist optimization transformations which make such
data difficult or impossible to generate. (In particular, it is
unlikely to be easier to create specialized data like this if the
compiler can't be made to create first-class DWARF for the same probe
points / data values.)
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-09-18 19:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060917143623.GB15534@elte.hu>
[not found] ` <20060917153633.GA29987@Krystal>
[not found] ` <20060918000703.GA22752@elte.hu>
[not found] ` <450DF28E.3050101@opersys.com>
[not found] ` <20060918011352.GB30835@elte.hu>
[not found] ` <20060918122527.GC3951@redhat.com>
[not found] ` <20060918150231.GA8197@elte.hu>
[not found] ` <1158594491.6069.125.camel@localhost.localdomain>
[not found] ` <20060918152230.GA12631@elte.hu>
[not found] ` <1158596341.6069.130.camel@localhost.localdomain>
[not found] ` <20060918161526.GL3951@redhat.com>
[not found] ` <1158598927.6069.141.camel@localhost.localdomain>
2006-09-18 19:11 ` Vara Prasad
2006-09-18 19:26 ` Alan Cox
2006-09-18 19:40 ` Frank Ch. Eigler [this message]
2006-09-18 20:29 ` Vara Prasad
2006-10-06 5:33 ` Steven Rostedt
2006-10-06 13:03 ` Frank Ch. Eigler
2006-10-06 14:23 ` Steven Rostedt
2006-10-06 23:17 ` Jeremy Fitzhardinge
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=20060918193952.GR3951@redhat.com \
--to=fche@redhat.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@suse.de \
--cc=hch@infradead.org \
--cc=jes@sgi.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mbligh@mbligh.org \
--cc=michel.dagenais@polymtl.ca \
--cc=mingo@elte.hu \
--cc=prasadav@us.ibm.com \
--cc=richardj_moore@uk.ibm.com \
--cc=systemtap@sourceware.org \
--cc=tglx@linutronix.de \
--cc=wcohen@redhat.com \
--cc=zanussi@us.ibm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).