Displaying 20 results from an estimated 1000 matches similar to: "[LLVMdev] Mangler does not check for duplicate symbols?"
2011 Nov 30
2
[LLVMdev] Problem using a label to a MachineBasicBlock
Hi all,
I think that I came somewhat closer to a solution for splitting a
MachineBasicBlock for a PSEUDO_CALL_R instruction and having a label to the new MBB:
For following piece of code:
---
typedef int callme_t(int a, int b);
callme_t* c01;
int foo(int a, int b)
{
return c01(a,b); // MachineBasicBlock will be split at call instruction
}
---
I have initially following correspondence:
BB1
2011 May 23
2
[LLVMdev] Debug llc crash using bugpoint
Hi,
What is the best way to debug an llc crash using bugpoint?
I am getting the following crash that I would like to reduce
llc: /home/vadve/aggarwa4/llvm29/llvm-2.9/lib/MC/MCAsmStreamer.cpp:273:
virtual void<unnamed>::MCAsmStreamer::EmitLabel(llvm::MCSymbol*): Assertion
`Symbol->isUndefined() && "Cannot define a symbol twice!"' failed.
0 llc
2011 May 23
0
[LLVMdev] Debug llc crash using bugpoint
Do something like this:
bugpoint -run-llc <bitcode file> --tool-args -- <llc arguments>
Cameron
On May 23, 2011, at 1:33 PM, Arushi Aggarwal wrote:
> Hi,
>
> What is the best way to debug an llc crash using bugpoint?
>
> I am getting the following crash that I would like to reduce
>
> llc: /home/vadve/aggarwa4/llvm29/llvm-2.9/lib/MC/MCAsmStreamer.cpp:273:
2011 Mar 28
3
[LLVMdev] Accessing metadata & creating DIVariable
Hi,
I am wondering if someone can guide me in adding metadata to IR which
already contains some metadata. I am trying to add dbg.declare inst
for a local variable I added to a function. I used the DIBuilder to
build a DIVariable. When I try to compile llc fails with following
message.
llc: MCAsmStreamer.cpp:273: virtual
void<unnamed>::MCAsmStreamer::EmitLabel(llvm::MCSymbol*): Assertion
2017 Dec 27
1
Convert MachineInstr to MCInst in AsmPrinter.cpp
Hello everyone,
In the file *lib/CodeGen/AsmPrinter/AsmPrinter.cpp*, I would like to obtain
an MCInst corresponding to its MachineInstr. Can anyone tell me a way to do
that?
If that is not possible, then, I would like to know if a given MachineInstr
is an *lea *instruction and I would like to know if the symbol involved
with this lea instruction is a jump-table.
For instance, given a
2012 Nov 01
1
[LLVMdev] emitting dwarf debug info on mach fails with assert
Compiling the IR code at http://pastebin.com/hSwdLdD0 for target triple
x86_64-apple-macosx
fails with :
assert(Symbol->isUndefined() && "Cannot define a symbol twice!");
`anon'::MCMachOStreamer::EmitLabel(llvm::MCSymbol * Symbol)
llvm::DwarfDebug::emitDebugInfo() Line 1752 + 0x3c bytes C++
llvm::DwarfDebug::endModule() Line 865 C++
2013 Jan 07
0
[LLVMdev] How to output a .S *and* a .OBJ file?
Hi,
I'm embarrassed that I can't figure this out... I have a compiler that
outputs my module in either .s assembly format or .obj binary format,
either one works just fine. But if I try to output both of them by adding
passes, LLVM throws an Assert:
void WinCOFFStreamer::EmitLabel(MCSymbol *Symbol) {
assert(Symbol->isUndefined() && "Cannot define a symbol
2010 Sep 18
2
[LLVMdev] Non-standard labels
Hi all,
I am emitting code for assembler which wants non-standard text for
labels (not just "LABEL:"). One way would be to override all methods
of AsmPrinter which call MCStreamer::EmitLabel but this is too
painful. I can think of two solutions:
1) add AsmPrinter::EmitLabel which calls Streamer by default but may
be overriden in target AsmPrinters
2) Register my own instance of
2010 Sep 18
0
[LLVMdev] Non-standard labels
On Sep 18, 2010, at 8:14 AM, Yuri Gribov wrote:
> Hi all,
>
> I am emitting code for assembler which wants non-standard text for
> labels (not just "LABEL:"). One way would be to override all methods
> of AsmPrinter which call MCStreamer::EmitLabel but this is too
> painful. I can think of two solutions:
>
> 1) add AsmPrinter::EmitLabel which calls Streamer by
2013 Sep 25
1
[LLVMdev] arm64 / iOS support
Attached is a working patch set for llvm to be able to emit arm64
(currently as triple aarch64-apple-ios) mach-o object files, in case
someone is interested. I'm not sure if the llvm maintainers want the
patch given the previous message that there's going to be an official
patch set from apple to support this, but here is mine.
What works (tested on an iPhone 5S):
* objc strings,
2012 Jul 31
1
[LLVMdev] How to create a mangler instance from target machine?
Dear LLVM,
Might be a easy question for someone, but not for me now. Consider there is
a TargetMachine instance. Having this target, how could you get a
corresponding Mangler class instance?
Mangler depends on MCContext, which is connected with LLVMTargetMachine
inherited from TargetMachine. However, LLVMTargetMachine is only available
for targets machines implementations, and not available
2010 Sep 18
2
[LLVMdev] Non-standard labels
Chris,
I want to emit code for target which uses non-standard assembler which
wants labels to look like
LAB nop
instead of
LAB:
I can not do this because labels are emitted by
MCAsmStreamer::EmitLabel which can not be overriden.
Best regards,
Yuri
2012 Mar 13
3
[LLVMdev] Your commit 103140
Hi Chris, your commit 103140 broke PR397 for llvm-gcc (in LLVM 2.9) and
dragonegg. In the PR, asm renaming creates two linkonce functions with
the same asm name (in the IR they are @"\01lstat64" and "@lstat64". What
used to happen is that they were both output to the assembler file, both
with the name lstat64, exactly like GCC does. The assembler and linker
are perfectly
2016 Jan 21
4
Is there a reason why MCAsmStreamer class doesn't have its own .h file?
Does anybody know if there is a particular reason why MCAsmStreamer doesn't
have its own .h file?
https://github.com/llvm-mirror/llvm/blob/0e66a5f53c74056f95d178c86531d7d9cfb23da9/lib/MC/MCAsmStreamer.cpp#L41
It seems like it is a good idea to have this class declared as its own
module ( its own .cpp and .h files). That would make it easier to inherit
from it if there is a need (like in my
2010 Sep 19
0
[LLVMdev] Non-standard labels
On Sep 18, 2010, at 10:52 AM, Yuri Gribov wrote:
> Chris,
>
> I want to emit code for target which uses non-standard assembler which
> wants labels to look like
> LAB nop
> instead of
> LAB:
>
> I can not do this because labels are emitted by
> MCAsmStreamer::EmitLabel which can not be overriden.
Is this just a textual/syntactic thing? If so, you should add a
2012 Oct 17
0
[LLVMdev] R_ARM_ABS32 disassembly with integrated-as
Hi Jim,
The diff below is not intended to be a patch, but a starting point.
It is the shortest path (I hope) to getting LLVM to emit ARM mapping
symbols to the ELF without changing any shared interfaces. Could you
have a look at the FIXME comments and offer some pointers on how to
get this code out of MCELFStreamer?
Thanks,
Greg
diff --git a/lib/MC/MCELFStreamer.cpp b/lib/MC/MCELFStreamer.cpp
2010 Jul 16
0
[LLVMdev] Win32 COFF Support - Patch 3
Hi Michael,
Overall patch looks good. I do have a few comments below. My main
comment is please try to make the style match that used in the
MCMachOStreamer more closely. I intend to refactor more functionality
into the base MCObjectStreamer class, and having them use consistent
idioms makes this easier; specific instances are included in the
comments:
--
> diff --git
2011 Nov 25
0
[LLVMdev] Where does LLVM mangle characters from llvm-ir names while generating native code?
On Nov 25, 2011, at 2:22 PM, bigcheesegs at gmail.com wrote:
> In the case I posted I had removed that line, however, you still get the __3F_ in the generated assembly with it.
Huh. It only seems to happen with a Windows triple or a Linux triple. Doesn't happen with a Mac triple, though--probably because the Darwin assembler supports quoted symbols (i.e. you can enclose an identifier in
2009 Sep 17
1
[LLVMdev] Patch for PR4776
Hello,
This patch against svn r82147 "fixes" PR4776. Certain targets (e.g.,
MSP430) allow a symbol to start with a number, e.g. "0x0021"; you can
say stuff like "mov.b &0x0021, r15" to copy a byte from memory address
0x0021 to register r15. LLVM had been generating this ill-formed code
instead:
mov.b &_30_x0021, r15 # note ASCII '0' has
2011 Nov 26
1
[LLVMdev] Where does LLVM mangle characters from llvm-ir names while generating native code?
On Fri, Nov 25, 2011 at 1:47 PM, Charles Davis <cdavis at mymail.mines.edu> wrote:
>
> On Nov 25, 2011, at 2:22 PM, bigcheesegs at gmail.com wrote:
>
>> In the case I posted I had removed that line, however, you still get the __3F_ in the generated assembly with it.
> Huh. It only seems to happen with a Windows triple or a Linux triple. Doesn't happen with a Mac triple,