public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: John Mellor-Crummey <johnmc@rice.edu>, elfutils-devel@sourceware.org
Cc: Jonathon Anderson <janderson@rice.edu>, Xiaozhu Meng <xm13@rice.edu>
Subject: Re: [PATCH] (v2) read inlining info in an NVIDIA extended line map
Date: Fri, 05 Nov 2021 10:34:38 +0100	[thread overview]
Message-ID: <7b7217036e620e60f9da97c79cf5e98b6a1aedc8.camel@klomp.org> (raw)
In-Reply-To: <C144CB95-588C-40AE-ADC0-C85E8A71837A@rice.edu>

Hi,

On Thu, 2021-11-04 at 16:41 -0500, John Mellor-Crummey via Elfutils-
devel wrote:
> [We would really like this patch in the forthcoming release]
> 
> Attached is a new version of the patch for reading inlining
> information encoded in an enhanced line map format used in NVIDIA GPU
> binaries for CUDA 11.2+.

It looks like the attachment is missing. Or the mailinglist removed it
for some reason, but I also didn't see it here:
https://sourceware.org/pipermail/elfutils-devel/2021q4/004307.html

Could you resent it?

Thanks,

Mark

> This is an updated version of a patch first submitted on Sept. 5. A
> copy of the original submission email is quoted below this note. 
> 
> Here I describe just the improvements to that patch that address
> Mark’s concerns:
> 
> (1) all of the code for handling NVIDIA DWARF extensions is always
> available; there is no special configuration switch needed.
> (2) all changes are bracketed by comments that mark them NVIDIA
> extensions
> (3) the DWARF extended opcodes have been renamed with names that
> include NVIDIA in them
> (4) the two new API functions to surface the new information have
> been improved to separate the interface result from the internal
> representation (at Mark’s request)
> 	(4a) the API for extracting the name of an inlined function in
> a DWARF line now returns a const char * instead of a string table
> index
> 	(4b) the API for extracting an inline “context” now returns a
> pointer to a DWARF line where the code is inlined rather than
> returning an unsigned int (an index into the line table that one
> could use to compute the pointer)
> (5) there are test cases for readelf and libdw that use a binary
> generated by NVIDIA’s compiler. the test cases include information
> about how the binary was generated




  reply	other threads:[~2021-11-05  9:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-06  0:07 Extension: " John Mellor-Crummey
2021-09-10 15:49 ` [PATCH] read inlining info in an NVIDIA extended line map (was: Extension ...) John Mellor-Crummey
2021-09-10 17:11   ` Mark Wielaard
2021-09-15 18:25     ` [PATCH] (revised) " John Mellor-Crummey
2021-11-04 21:41       ` [PATCH] (v2) read inlining info in an NVIDIA extended line map John Mellor-Crummey
2021-11-05  9:34         ` Mark Wielaard [this message]
2021-11-10 10:16         ` Mark Wielaard
2021-11-10 15:14           ` John Mellor-Crummey

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=7b7217036e620e60f9da97c79cf5e98b6a1aedc8.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=elfutils-devel@sourceware.org \
    --cc=janderson@rice.edu \
    --cc=johnmc@rice.edu \
    --cc=xm13@rice.edu \
    /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).