Re: [DynInst_API:] DynInst problem of generating extra spill code

[Tim Haines <thaines@xxxxxxxxxxx>]

    The github issue is https://github.com/dyninst/dyninst/issues/1523.
    I tagged you and Yasodha, so you should get updates automatically.
    
    Thanks.
    - Tim

On 9/11/23 1:03 PM, Tallent, Nathan R wrote:

No worries â please do so.

__________________________________________
Nathan R. Tallent, PhD
Scalable Computing & Data Team Lead
High Performance Computing Group
Pacific Northwest National Laboratory
509.372.4206 â https://hpc.pnnl.gov/people/tallent/

On Sep 11, 2023, at 10:43 AM, Tim Haines <thaines@xxxxxxxxxxx> wrote:

Check twice before you click! This email originated from outside PNNL.

Hi, Nathan.

Thanks for the detailed report. We like to use Github issues to track user reports. Are there any IP concerns with making the attached files public?

Thanks.
- Tim

On 9/8/23 3:00 PM, Tallent, Nathan R wrote:

Dear Bart,

You might recall that I mentioned a use of DynInst where instrumention is generated with with register saves/restores when none should be needed.

We have packaged a test case to illustrate the problem. 

A detailed description of the problem is in the hyperlink below. We are also happy to have a quick chat with one of your team members to make any needed clarifications.

Thank you!

__________________________________________
Nathan R. Tallent, PhD
Scalable Computing & Data Team Lead
High Performance Computing Group
Pacific Northwest National Laboratory
509.372.4206 â https://hpc.pnnl.gov/people/tallent/

Begin forwarded message:

From: "Suriyakumar, Yasodha" <yasodha@xxxxxxxx>

Subject: Re: DynInst problem of generating extra spill code

Date: September 7, 2023 at 12:13:07 PM PDT

To: "Tallent, Nathan R" <Nathan.Tallent@xxxxxxxx>

Cc: "Kilic, Ozgur" <okilic@xxxxxxx>, "Velugoti, Nanda K" <nanda.velugoti@xxxxxxxx>

Hello Nathan,

Link to the description of the issue is under (2) : https://github.com/pnnl/memgaze/tree/master/xlib#dyninst

I have attached the testcase with all the relevant files. I have included a copy of the README.txt from the testcase.

The testcase covers a correct mapping as well as the added spill code. If there is any additional information needed, let me know. If not, it can be sent to the Dyninst group.

Thanks,

Yasodha.

 

From: Tallent, Nathan R <Nathan.Tallent@xxxxxxxx>
Date: Thursday, August 17, 2023 at 9:35 AM
To: Suriyakumar, Yasodha <yasodha@xxxxxxxx>
Cc: Kilic, Ozgur <okilic@xxxxxxx>, Velugoti, Nanda K <nanda.velugoti@xxxxxxxx>
Subject: DynInst problem of generating extra spill code

[With Ozgurâs correct email â stupid mac mail still pulls pnnl]

 

Hi Yasodha,

 

I talked to Bart Miller (head of DynInst group) specifically about our problem of occasionally generating extra spill code. He said (a) it was not expected (as we expected and (b) they would be happy to take a look.

 

When there is a convenient moment, we should prepare a package showing the (a) the normal case and (b) anomalous case.

 

Thanks!

__________________________________________
Nathan R. Tallent, PhD
Scalable Computing & Data Team Lead
High Performance Computing Group
Pacific Northwest National Laboratory
509.372.4206 â https://hpc.pnnl.gov/people/tallent/

 

_______________________________________________
Dyninst-api mailing list
Dyninst-api@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/dyninst-api