SingleAccretion opened PR #9578 from SingleAccretion:DI-Decl
to bytecodealliance:main
:
Declarations must be consistent across compilation units, therefore, they cannot be GCed away from their parent DIEs (most likely ones defining a type). This is the same situation as with, e. g. class member variables (fields).
Fixes #9512.
SingleAccretion updated PR #9578.
SingleAccretion edited PR #9578:
Declarations must be consistent across compilation units, therefore, they cannot be GCed away from their parent type DIEs. This is the same situation as with, e. g. class member variables (fields).
Fixes #9512.
SingleAccretion edited PR #9578:
Declarations must be consistent across compilation units for any given type. This is the same situation as with, e. g. class member variables (fields).
Fixes #9512.
SingleAccretion edited PR #9578:
Declarations must be consistent across compilation units for any given type. This is the same situation as with, e. g. class member variables (fields).
Furthermore, even for ordinary C declarations, deleting them can theoretically mess up the expression evaluator (since a function that was supposed to be in scope no longer is).
Fixes #9512.
SingleAccretion edited PR #9578:
Declarations must be consistent across compilation units for any given type. This is the same situation as with, e. g. class member variables (fields).
Furthermore, even for ordinary C declarations, deleting them can theoretically mess up the expression evaluator (since a function that was supposed to be in scope no longer is). This is mostly a theoretical concern, however, as calling functions in the context of translated DWARF is currently deeply broken anyway.
Fixes #9512.
SingleAccretion updated PR #9578.
SingleAccretion has marked PR #9578 as ready for review.
SingleAccretion requested alexcrichton for a review on PR #9578.
SingleAccretion requested wasmtime-core-reviewers for a review on PR #9578.
SingleAccretion edited PR #9578:
Declarations must be consistent across compilation units for any given type. This is the same situation as with, e. g., class member variables (fields).
Furthermore, even for ordinary C declarations, deleting them can theoretically mess up the expression evaluator (since a function that was supposed to be in scope no longer is). This is mostly a theoretical concern, however, as calling functions in the context of translated DWARF is currently deeply broken anyway.
Fixes #9512.
SingleAccretion updated PR #9578.
SingleAccretion edited PR #9578:
Declarations must be consistent across compilation units for any given type. This is the same situation as with, e. g., class member variables (fields).
Furthermore, even for ordinary C declarations, deleting them can theoretically mess up the expression evaluator (since a function that was supposed to be in scope no longer is). This is mostly a theoretical concern, however, as calling functions in the context of translated DWARF is currently deeply broken anyway.
Fixes #9512.
I've also tweaked the dumping of DIE offsets for easier cross-referencing with llvm-dwarfump.
alexcrichton submitted PR review:
Thanks!
alexcrichton has enabled auto merge for PR #9578.
alexcrichton merged PR #9578.
Last updated: Dec 23 2024 at 12:05 UTC