Robin Voetter

> The return value must not be consistent inbetween builds, so a second build might return completly different numbers for the same types. Is the intention that the returned value...

After some extra thinking, Im completelt against possible nondeterminism at compile time. For a runtime value I think that it's fine provided that the result is stable across compiler runs...

If the value _is_ determinstic across runs, compiler versions, etc, I dont have a problem with it. In Auguste's proof of concept, the value is derived from a compiler-internal type...

With the ongoing parallelization of the compiler it would be nice if there was some test that the ID remains stable across compilations to avoid nondeterministic builds.

hipGraphics symbols are also missing

There is no reason that this support cannot be added, though. In fact, it is not too complex to capture the rgp trace via a HSA PM4 packet, which is...

I found out why: At least on my machine, cmake hangs without this when the right LLVM version is not found.

Any update on this?

I think it is worded like that too keep this separate from a proposal to allow more I/O for assembly in global contexts, which is currently not allowed I think.

## Background SPIR-V is a strongly typed IR format, like LLVM IR especially before LLVM removed pointee types. Most operations need to be ascribed with their result type. Like LLVM...