search for: asminfo

Displaying 13 results from an estimated 13 matches for "asminfo".

2011 Feb 12
4
[LLVMdev] [patch] Dwarf Debug info support for COFF object files
...mplementations for all existings Streamer (all but WinCOFF either forward or error on it) secrel-dwarf.patch updates dwarf printing code to make use of the new directive & DIE value where appropriate (this is where the bug fix is) coff-debug.patch turns the dwarf output on in the X86/COFF AsmInfo classes - Nathan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110212/19580f05/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: die.patch Type: applic...
2011 Jul 06
0
[LLVMdev] MCInstPrinter::printRegName
...r back to its corresponding dwarf register number in function InstPrinter->printRegName? I just want to have it output the same register number as before (the same output the false path would produce). void MCAsmStreamer::EmitRegisterName(int64_t Register) { if (InstPrinter) { const TargetAsmInfo &asmInfo = getContext().getTargetAsmInfo(); unsigned LLVMRegister = asmInfo.getLLVMRegNum(Register, true); InstPrinter->printRegName(OS, LLVMRegister); } else { OS << Register; } } My current implementation of printRegName which I copied from other backends (X86, ARM a...
2014 Mar 06
4
[LLVMdev] llvm-mc and endianess.
Hi, As a first step to port the LLVM chain on an in-house big-endian processor, I'm integrating the native assembler as a new '-assemble -arch=' in llvm-mc. All work quite well, I have a correct output ELF format except that generated code is little-endian. I've understood that the endianess of the LLVM chain is controlled by the DataLayout class, but it appear to me that llvm-mc
2012 Apr 02
1
[LLVMdev] Adding a Yasm ASM printer
...s that yasm doesn't understand. I've made a X86YasmInstPrinter, and added it to the x86.td, as a new variant, and due to it having a new Variant number, I'm having to edit all the X86*.td files and add the extra variant's descriptions in the { | } blocks. I've also added a new ASMInfo class with the required changes for yasm. Now what is worrying me is the number of .td files I'm having to touch, and most of the changes are adding a variant with exactly the same code as the intel variant, there are just a few cases that a slightly different. I'm about 1/4 way through...
2011 Feb 24
0
[LLVMdev] [patch] Dwarf Debug info support for COFF object files
...gs Streamer (all but WinCOFF either forward or error on it) > > secrel-dwarf.patch > updates dwarf printing code to make use of the new directive & DIE value where appropriate (this is where the bug fix is) > > coff-debug.patch > turns the dwarf output on in the X86/COFF AsmInfo classes This patches look fine. I am curious, how are you testing debug info support for COFF ? - Devang
2011 Nov 26
1
[LLVMdev] Where does LLVM mangle characters from llvm-ir names while generating native code?
...though--probably because the Darwin assembler supports quoted symbols (i.e. you can enclose an identifier in quotes). Maybe Joe is right, and you should change the LLVM mangler to not mangle '?' chars (if the assembler can handle it). Or maybe we should see if GAS supports quoted symbols (MCAsmInfo::doesAllowQuotesInName()). > > Chip So setting AllowQuotesInName=true gets the correct names in the output. However, it breaks MinGW. The issue is of course that MCAsmInfo mixes both assembler and object file format capabilities. Allowing quoted names has nothing to do with COFF ;/. So it se...
2011 Feb 24
2
[LLVMdev] [patch] Dwarf Debug info support for COFF object files
...inCOFF either forward or error on it) >> >> secrel-dwarf.patch >> updates dwarf printing code to make use of the new directive & DIE value where appropriate (this is where the bug fix is) >> >> coff-debug.patch >> turns the dwarf output on in the X86/COFF AsmInfo classes > > This patches look fine. I am curious, how are you testing debug info support for COFF ? Well, this patch fails following FE tests on darwin. LLVM :: FrontendC++/2006-11-06-StackTrace.cpp LLVM :: FrontendC++/2006-11-30-Pubnames.cpp LLVM :: FrontendC++/2010-08-31-ByVal...
2013 Feb 27
2
[LLVMdev] TargetMCAsmInfo.cpp Question
I'd like to set all Global Symbols to be prefixed with '_' ; however, when I set GlobalPrefix in TargetMCAsmInfo.cpp, this also applies to library calls (adds extra underscore which makes 3 so linkage failure), which I don't want. Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130227/6b8aebdb/attachment.ht...
2013 Feb 27
0
[LLVMdev] TargetMCAsmInfo.cpp Question
...ry routines), for example, something like __subsf3. What's the best way to do this? On Wed, Feb 27, 2013 at 11:05 AM, Ryan Taylor <ryta1203 at gmail.com> wrote: > I'd like to set all Global Symbols to be prefixed with '_' ; however, when > I set GlobalPrefix in TargetMCAsmInfo.cpp, this also applies to library > calls (adds extra underscore which makes 3 so linkage failure), which I > don't want. > > Thanks. > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/2013022...
2011 Feb 24
0
[LLVMdev] [patch] Dwarf Debug info support for COFF object files
...or error on it) >>> >>> secrel-dwarf.patch >>> updates dwarf printing code to make use of the new directive & DIE value where appropriate (this is where the bug fix is) >>> >>> coff-debug.patch >>> turns the dwarf output on in the X86/COFF AsmInfo classes >> >> This patches look fine. I am curious, how are you testing debug info support for COFF ? > > Well, this patch fails following FE tests on darwin. > LLVM :: FrontendC++/2006-11-06-StackTrace.cpp > LLVM :: FrontendC++/2006-11-30-Pubnames.cpp > LLVM :...
2011 Nov 25
0
[LLVMdev] Where does LLVM mangle characters from llvm-ir names while generating native code?
...though--probably because the Darwin assembler supports quoted symbols (i.e. you can enclose an identifier in quotes). Maybe Joe is right, and you should change the LLVM mangler to not mangle '?' chars (if the assembler can handle it). Or maybe we should see if GAS supports quoted symbols (MCAsmInfo::doesAllowQuotesInName()). Chip > > Sent from my iPhone > > On Nov 25, 2011, at 2:15 PM, Charles Davis <cdavis at mymail.mines.edu> wrote: > >> >> On Nov 25, 2011, at 8:39 AM, Michael Spencer wrote: >> >>> So I was taking a look at Microsoft C+...
2011 Nov 25
2
[LLVMdev] Where does LLVM mangle characters from llvm-ir names while generating native code?
In the case I posted I had removed that line, however, you still get the __3F_ in the generated assembly with it. Sent from my iPhone On Nov 25, 2011, at 2:15 PM, Charles Davis <cdavis at mymail.mines.edu> wrote: > > On Nov 25, 2011, at 8:39 AM, Michael Spencer wrote: > >> So I was taking a look at Microsoft C++ ABI support while on vacation, >> and ran into a major
2010 Jun 21
2
[LLVMdev] MC: Object file specific parsing
...rser/AsmLexer.h" #include "llvm/MC/MCParser/AsmCond.h" #include "llvm/MC/MCParser/MCAsmParser.h" +#include "llvm/MC/MCParser/MCParsedAsmOperand.h" #include "llvm/MC/MCSectionMachO.h" #include "llvm/MC/MCStreamer.h" #include "llvm/MC/MCAsmInfo.h" @@ -36,10 +37,11 @@ class TargetAsmParser; class Twine; class AsmParser : public MCAsmParser { -private: +protected: AsmLexer Lexer; MCContext &Ctx; MCStreamer &Out; +private: SourceMgr &SrcMgr; TargetAsmParser *TargetParser; @@ -88,14 +90,23 @@ public:...