Thanks Jeff. No, CodeView is effectively Windows-specific - it relies on PE for
reporting the PDB filename, and COFF for the .secidx relocation. I might look
into moving these bits into the config once I get down to plumbing it for
aarch64-w64-mingw32.
Mark
On 14/08/2024 05:09, Jeff Law wrote:
On 8/12/24 6:24 PM, Mark Harmstone wrote:
Outputs CodeView S_LDATA32 symbols, for static variables within
functions, along with S_BLOCK32 and S_END for the beginning and end of
lexical blocks.
gcc/
* dwarf2codeview.cc (enum cv_sym_type): Add S_END and S_BLOCK32.
(write_local_s_ldata32): New function.
(write_unoptimized_local_variable): New function.
(write_s_block32): New function.
(write_s_end): New function.
(write_unoptimized_function_vars): New function.
(write_function): Call write_unoptimized_function_vars.
This series is fine. I'm not particularly jazzed about how much target
specific data shows up in patch #2. It's probably safe to assume the mapping
of register number of the codeview number doesn't match the dwarf map. It's
probably also safe to assume we're not supporting codeview on any targets other
than x86 and ix86?
jeff
