search for: getvariablelocation

...the DbgVariableIntrinsic class) > expresses everything in terms of the variables location, whereas > implicit pointers don't have a location as they represent an extra > level of indirection. This is best demonstrated by the change to > IntrinsicInst.cpp in this patch [0] -- calling getVariableLocation on > any normal dbg.value will return the locations Value, but if it's an > implicit pointer then you'll get the meaningless MetadataAsValue > wrapper back instead. This isn't the variable location, might surprise > existing handlers of dbg.values, and just seems a little of...

Hey folks, Would you all mind having a bit of a design discussion around the feature both at the DWARF level and the LLVM implementation? It seems like what's currently being proposed/reviewed (based on the DWARF feature as spec'd) is a pretty big change & I'm not sure I understand the motivation, exactly. The core point of my confusion: Why does describing the thing a pointer

...>> expresses everything in terms of the variables location, whereas > >> implicit pointers don't have a location as they represent an extra > >> level of indirection. This is best demonstrated by the change to > >> IntrinsicInst.cpp in this patch [0] -- calling getVariableLocation on > >> any normal dbg.value will return the locations Value, but if it's an > >> implicit pointer then you'll get the meaningless MetadataAsValue > >> wrapper back instead. This isn't the variable location, might surprise > >> existing handlers of db...