search for: mcasminfomicrosoft

Displaying 3 results from an estimated 3 matches for "mcasminfomicrosoft".

2012 Oct 26
5
[LLVMdev] Debug information under windows
...MCAsmInfoCOFF.cpp Thu Oct 18 12:41:27 2012 +0200 @@ -38,6 +38,10 @@ HasMicrosoftFastStdCallMangling = true; SupportsDataRegions = false; + + DwarfUsesLabelOffsetForRanges = false; + DwarfRequiresRelocationForSectionOffset = false; + DwarfUsesRelocationsForStringPool = false; } void MCAsmInfoMicrosoft::anchor() { }
2012 Oct 26
0
[LLVMdev] Debug information under windows
...> @@ -38,6 +38,10 @@ > HasMicrosoftFastStdCallMangling = true; > > SupportsDataRegions = false; > + > + DwarfUsesLabelOffsetForRanges = false; > + DwarfRequiresRelocationForSectionOffset = false; > + DwarfUsesRelocationsForStringPool = false; > } > > void MCAsmInfoMicrosoft::anchor() { } > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
2012 Nov 19
0
[LLVMdev] Debug information under windows
...@@ -38,6 +38,10 @@ > HasMicrosoftFastStdCallMangling = true; > > SupportsDataRegions = false; > + > + DwarfUsesLabelOffsetForRanges = false; > + DwarfRequiresRelocationForSectionOffset = false; > + DwarfUsesRelocationsForStringPool = false; > } > > void MCAsmInfoMicrosoft::anchor() { } > Hello again, "fix" from my previous message was helpful only for one compilation unit, but was working incorrectly in case when more CUs were linked together. Since the bug I've linked seems to still be unresolved, I'm sending my solution to it. Basically...