Re: [Valgrind-users] Question about Valgrind tool in Intel new platform

2022-04-21 Thread John Reiser
On 4/20/22 05:18, Yang Zhong wrote: The AMX is the NEW feature in Intel new platform and from host, we can find below cpu flags: amx_bf16, amx_tile, amx_int8 The SPEC can be found in:

Re: [Valgrind-users] Question about Valgrind tool in Intel new platform

2022-04-20 Thread Tom Hughes via Valgrind-users
On 20/04/2022 13:41, Tom Hughes via Valgrind-users wrote: Again until we know what "AMX features" are it's impossible to comment in any detail. So apparently AMX is this: https://en.wikipedia.org/wiki/Advanced_Matrix_Extensions So not only is it new instructions, it is new two dimensional

Re: [Valgrind-users] Question about Valgrind tool in Intel new platform

2022-04-20 Thread Tom Hughes via Valgrind-users
On 20/04/2022 13:18, Yang Zhong wrote: On Wed, Apr 20, 2022 at 09:37:17AM +0100, Tom Hughes wrote: On 20/04/2022 09:01, Yang Zhong wrote: So, from above issue in Intel new platform, the valgrind need do some enablings to be compatible with on new platform? Seems valgrind tool can't identify

Re: [Valgrind-users] Question about Valgrind tool in Intel new platform

2022-04-20 Thread Yang Zhong
On Wed, Apr 20, 2022 at 09:37:17AM +0100, Tom Hughes wrote: > On 20/04/2022 09:01, Yang Zhong wrote: > > >So, from above issue in Intel new platform, the valgrind need do some > >enablings to be compatible > >with on new platform? Seems valgrind tool can't identify the real HW > >platform

Re: [Valgrind-users] Question about Valgrind tool in Intel new platform

2022-04-20 Thread Tom Hughes via Valgrind-users
On 20/04/2022 09:01, Yang Zhong wrote: So, from above issue in Intel new platform, the valgrind need do some enablings to be compatible with on new platform? Seems valgrind tool can't identify the real HW platform because cpuid can't read correct register value. thanks! When running under

Re: [Valgrind-users] Question about Valgrind tool implementation

2013-09-09 Thread Philippe Waroquiers
On Mon, 2013-09-09 at 10:50 +0900, Chang-Jae Lee wrote: The first definition of variable c is at line 11. We then suppress the line 11, and subsequent use of variable c(at line 12) The above defines what to do speaking in terms of source lines, while valgrind works at binary level. There is

Re: [Valgrind-users] Question about Valgrind tool implementation

2013-09-08 Thread Chang-Jae Lee
On Fri, Sep 6, 2013 at 5:43 AM, Philippe Waroquiers philippe.waroqui...@skynet.be wrote: On Thu, 2013-09-05 at 16:01 +0900, Chang-Jae Lee wrote: Not too sure about what you mean with the above. Valgrind works at binary level, it does not really have a notion of statement. For example, if

Re: [Valgrind-users] Question about Valgrind tool implementation

2013-09-05 Thread Philippe Waroquiers
On Thu, 2013-09-05 at 16:01 +0900, Chang-Jae Lee wrote: Hi, I am a grad-student in KAIST, and I'm working on a project for finding bugs or errors. Currently I'm following a routine from the paper Execution Suppression: An Automated Iterative Technique for Locating Memory Errors. It is

Re: [Valgrind-users] Question about Valgrind

2012-03-23 Thread Eliot Moss
On 3/23/2012 9:10 AM, Hamid Reza Khaleghzadeh wrote: Hi, I have some questions about Valgrind tool. I would be thankful if answer me. 1- I want to know does Valgrind support Pthread and openMP programs? 2- I need a tool that traces my multi-threaded program and creates memory trace of the

Re: [Valgrind-users] Question about Valgrind

2012-03-23 Thread Eliot Moss
On 3/23/2012 12:21 PM, Hamid Reza Khaleghzadeh wrote: Hi Dear Eliot, I added valgrind-users back so that all can follow the email thread. Thanks for your answer. You said that Valgrind does support multiple threads, but runs only one thread at a time. Suppose a two threaded application.

Re: [Valgrind-users] Question about Valgrind

2012-03-23 Thread Julian Seward
In sum, you should get one *possible* execution, but it won't necessarily be one typical of truly concurrent execution. (Just because you have threads that are *runnable* at the same time does not mean that they actually run *concurrently* in a real system, unless you guarantee multuple