search for: noicf

...n obj and then by adding the .debug$H with llvm-objcopy we might get over the limit (I didn't see any code on the obj coff writer to deal with that). For the linker I was using: /FUNCTIONPADMIN:6 /MACHINE:X64 /DEBUG:GHASH -time /INCREMENTAL:NO But I'm going to be adding: /OPT:NOREF /OPT:NOICF because maybe the wrong callstacks might be related to ICF. I will try to get a simple test case to show this erros, but its difficult, debugging mostly works, its just on some complicated cases that it stops working, but we might be able to find a small repro case. This email was to get to know h...

Hi, We are starting to test binaries generated by lld on windows and we notices that sometimes the visual studio debugger can't see the content of variables or gets the call stack wrong for deeply nested or complex types. Did anyone else have the same problems, or any way to try to figure out what is missing? I tried llvm-pdbutil dump -symbols but there is a lot of small diferences on