Displaying 6 results from an estimated 6 matches for "asmwriterflavor".
2016 Nov 11
2
initialization-order-fiasco in MCTargetDesc/X86MCAsmInfo.cpp
...r-fiasco on
address 0x000002ef41d8 at pc 0x0000009d1aa5 bp 0x7ffd0cd72b50 sp
0x7ffd0cd72b48
READ of size 4 at 0x000002ef41d8 thread T0
#0 0x9d1aa4 in getValue
/mnt/b/sanitizer-buildbot3/sanitizer-x86_64-linux-fast/build/llvm/include/llvm/Support/CommandLine.h:1229:38
#1 0x9d1aa4 in operator AsmWriterFlavorTy
/mnt/b/sanitizer-buildbot3/sanitizer-x86_64-linux-fast/build/llvm/include/llvm/Support/CommandLine.h:1233
#2 0x9d1aa4 in llvm::X86ELFMCAsmInfo::X86ELFMCAsmInfo(llvm::Triple
const&) /mnt/b/sanitizer-buildbot3/sanitizer-x86_64-linux-fast/build/llvm/lib/Target/X86/MCTargetDesc/X86MCAsmInfo.c...
2005 Feb 18
7
[LLVMdev] LLVM built on VS C++ 2005
...eps:
1. Define a new subclass of X86IntelAsmPrinter in the
lib/Target/X86/X86AsmPrinter class, name it X86NASMAsmPrinter or
something.
2. In the subclass, change any behaviors that you don't like (e.g.
change it to use the appropriate directives for NASM).
3. Add this option to the AsmWriterFlavor variable at the top of the file,
so we can say "-x86-asm-syntax=nasm"
4. Modify X86TargetMachine.cpp so that addPassesToEmitAssembly() create a
NASM target machine if the target triple stored in the module is set to
something windows like. I don't know what the standard t...
2005 Feb 18
0
[LLVMdev] LLVM built on VS C++ 2005
...subclass of X86IntelAsmPrinter in the
> lib/Target/X86/X86AsmPrinter class, name it X86NASMAsmPrinter or
> something.
> 2. In the subclass, change any behaviors that you don't like (e.g.
> change it to use the appropriate directives for NASM).
> 3. Add this option to the AsmWriterFlavor variable at the top of the file,
> so we can say "-x86-asm-syntax=nasm"
> 4. Modify X86TargetMachine.cpp so that addPassesToEmitAssembly() create a
> NASM target machine if the target triple stored in the module is set to
> something windows like. I don't know wh...
2005 Feb 18
0
[LLVMdev] LLVM built on VS C++ 2005
>> I thought Whidbey would really be upto the job, obviously not.
>
> Well, we don't know until someone tries.
Oh, well we have got a bug to report to Microsoft then !
I still may carry on implementing any mods on the VS2003 port over to 2005
so we know where we are with that. There may well be a second beta so it
would be good to get any problems in and reported to Microsoft in
2005 Feb 18
3
[LLVMdev] LLVM built on VS C++ 2005
Aaron Gray wrote:
>> GCC is smart enough to realize it doesn't return. That's because the
>> declaration of abort() is decorated with __attribute__((__noreturn__)).
>>
>> So is GCC smarter than VC++? As it turns out, in VC++ the
>> declaration of abort() is decorated with __declspec(noreturn).
>>
>> Whidbey is not stricter than 2003, it is
2017 Jun 21
6
RFC: Cleaning up the Itanium demangler
...;},
{"_ZL8NoFusing", "NoFusing"},
{"_ZL17PrintFailedFusing", "PrintFailedFusing"},
{"_ZL16ReMatPICStubLoad", "ReMatPICStubLoad"},
{"_ZL19JITCompilerFunction", "JITCompilerFunction"},
{"_ZL15AsmWriterFlavor", "AsmWriterFlavor"},
{"_ZN4llvm12_GLOBAL__N_1L6CCRVTsE", "llvm::(anonymous namespace)::CCRVTs"},
{"_ZN4llvm12_GLOBAL__N_1L14CONTROL_REGVTsE", "llvm::(anonymous namespace)::CONTROL_REGVTs"},
{"_ZN4llvm12_GLOBAL__N_1L12DEBUG_...