Displaying 20 results from an estimated 7000 matches similar to: "[LLVMdev] Raising inline-asm blocks"
2013 Jun 26
1
[LLVMdev] Inline asm call argument mismatch?
Hello,
In the following code snippet:
%tmp49 = call i64 asm "movq %gs:${1:P},$0", "=r,im,,~{fpsr},~{flags}"(i64*
@kernel_stack) #6, !dbg !6625, !srcloc !5841
I would expect for the inline asm call to receive two arguments because of
the ${1:P} corresponding to a %P1 that will append the $1 to %%gs:.
Can someone explain why there is only one argument in this call?
Moreover,
2013 Apr 21
3
[LLVMdev] trying to generate a simple inline asm
I'm trying to just emit simple inline assembler (no constraints, inputs,
etc.)
Can anyone point me to an example of this..?
This is corresponding to:
__asm__ ("mfc1 $4,$f12");
This is what I tried but it's not correct.
std::vector<llvm::Type *> AsmArgTypes;
llvm::FunctionType *AsmFTy =
llvm::FunctionType::get(Type::getVoidTy(FStub->getContext()),
2011 Aug 31
1
[LLVMdev] FP Stack overflow with inline asm
Hi LLVM hackers,
when switching one of our projects to LLVM we discovered some strange behavior. We tracked the issue down to the following test case:
int main()
{
double v = 0.84711;
int r;
__asm__("fistl %0": "=m"(r) : "t"(v));
return r;
}
The (relevant) clang generated asm looks like this:
fldt 0.84711
## InlineAsm Start
fistl -4(%ebp)
## InlineAsm End
2016 Oct 29
1
Problems with Inline ASM expressions generated in the back end
Hello.
I generated in the back end by hand (in C++ code, not with TableGen) some fancy
assembly code using Inline ASM expressions and if I use 2 functions in my source code (but
NOT just 1 function; I will not present the functions, but each requires me to generate an
Inline ASM expression) I get this error at compilation (at scheduling):
BB#0: derived from LLVM BB %entry
2008 Jun 06
2
[LLVMdev] Trouble with inline asm
Hi all,
I'm having some trouble with inline asm expressions, more specifically
how to create the right FunctionType for a given constraint set.
So far it has worked well for inputs, but not for outputs. The inline
asm support in this language (which is D, LLVMDC[1]) is through asm
*statements*.
I never have inline asm *expressions*, and outputs are always via memory.
I D my test looks like
2008 Jun 06
0
[LLVMdev] Trouble with inline asm
On Fri, Jun 6, 2008 at 6:32 AM, Tomas Lindquist Olsen
<tomas.l.olsen at gmail.com> wrote:
> Hi all,
>
> I'm having some trouble with inline asm expressions, more specifically
> how to create the right FunctionType for a given constraint set.
> So far it has worked well for inputs, but not for outputs. The inline
> asm support in this language (which is D, LLVMDC[1]) is
2010 Mar 16
0
[LLVMdev] LLVM-GCC generating too much code from inline assembly
You may find it helpful to reference http://www.ibiblio.org/gferg/ldp/GCC-Inline-Assembly-HOWTO.html. In particular, the information regarding clobbers and constraints.
Generally speaking, it's best not to use inline assembly at all. What are you trying to do that you find it necessary?
On Mar 16, 2010, at 12:30 AM, Fred / Kettch wrote:
> Hi,
>
> I recently switched to LLVM-GCC
2010 Mar 16
3
[LLVMdev] LLVM-GCC generating too much code from inline assembly
Hi,
I recently switched to LLVM-GCC 4.2 on OS X, to go around a bug caused by
gcc with optimized code. Unfortunately, I ran into another weird problem on
LLVM-GCC. In my code, there's a file with a bunch of inline assembly blocks,
that worked fine with GCC 4.2. Now, when compiling with LLVM-GCC 4.2, weird
things happen.
Here's an example: (the blocks are larger than that, but a single
2013 Jun 20
1
[LLVMdev] opt fails with assertion in Attributes.cpp
Hi Bill,
With the latest llvm version I'm getting the following error:
opt -instnamer < core-device.c.bc > core-device.o.bc
Attribute 'nobuiltin' only applies to functions!
void (%struct.fw_csr_iterator*, i32*)* @fw_csr_iterator_init
Broken module found, compilation aborted!
0 opt 0x0000000001914bf1 llvm::sys::PrintStackTrace(_IO_FILE*)
+ 38
1 opt
2009 Jun 30
2
[LLVMdev] modifying llc asm output
Hi
I am trying to modify the llc in that way:
subf 3, 5, 3 subf 3, 5, 3
stw 3, 44(1) stw 3, 44(1)
# InlineAsm
Start
--> isync
2010 Sep 21
0
[LLVMdev] inline asm constraints examples/tests
On Sep 21, 2010, at 2:45 PMPDT, John Thompson wrote:
> fatal error: error in backend: Ran out of registers during register allocation!
> Please check your inline asm statement for invalid constraints:
> INLINEASM <es:>, 0, 10, %reg16396<def>, 10, %reg16397<def>, 10, %reg16398<def>, 10, %reg16399<def>, 10, %reg16400<def>, 10, %reg16401<def>,10,
2013 Jun 17
2
[LLVMdev] opt fails with assertion in Attributes.cpp
Hello,
I'm getting an error when running opt with what seems to be a valid
bytecode file compiled from one the Linux Kernel files.
The error is:
opt: /home/scratch/llvm/lib/IR/Attributes.cpp:119: llvm::StringRef
llvm::Attribute::getKindAsString() const: Assertion `isStringAttribute() &&
"Invalid attribute type to get the kind as a string!"' failed.
I send you in attach
2010 Aug 25
2
[LLVMdev] [REQUEST FOR FEEDBACK] Inline asm multiple alternative constraints
Hi,
I'm looking for some feedback on the changes represented in the attached
patches, which I'll describe below.
I'm sending this to both the LLVM and Clang list because it affects both,
though the main focus here is LLVM.
Basically, I've partially implemented some changes for choosing multiple
alternative constraints largely on the LLVM side.
The Clang change is to output the
2010 Aug 27
0
[LLVMdev] [REQUEST FOR FEEDBACK] Inline asm multiple alternative constraints
On Aug 25, 2010, at 12:45 PM, John Thompson wrote:
> Hi,
>
> I'm looking for some feedback on the changes represented in the
> attached patches, which I'll describe below.
>
> I'm sending this to both the LLVM and Clang list because it affects
> both, though the main focus here is LLVM.
> Basically, I've partially implemented some changes for choosing
2013 Sep 14
1
[LLVMdev] Publication: LLVMVF: A Generic Approach for Verification of Multicore Software
Dear all,
I'm happy to share a recent publication on a bounded model checker for
concurrent programs represented in LLVM IR that integrates the verification
framework that I'm developing:
Marcelo Sousa, and Alper Sen, LLVMVF: A Generic Approach for Verification
of Multicore Software. Journal of Electronic Testing: Theory and
Applications, September 2013. (
2009 Jun 30
0
[LLVMdev] modifying llc asm output
On Tue, Jun 30, 2009 at 8:33 AM, Michael
Graumann<MichaelGraumann at gmx.net> wrote:
> Hi
>
> I am trying to modify the llc in that way:
>
>
>
> subf 3, 5, 3 subf 3, 5, 3
>
> stw 3, 44(1) stw 3, 44(1)
>
> # InlineAsm
2010 Sep 21
3
[LLVMdev] inline asm constraints examples/tests
Dale,
Sorry, I see you did say I should run the gcc tests. I apologize for
forgetting this. I'll work on getting them to run here.
Chris et. all,
I have a fix for the assertion failure in the enclosed llvmmultalt8.patch
file. I didn't realize the input constraints could have different numbers
of alternatives from the outputs, which now makes sense. The pr20314-2.c
file now compiles
2008 Jun 07
1
[LLVMdev] Trouble with inline asm
On Fri, Jun 6, 2008 at 9:29 PM, Eli Friedman <eli.friedman at gmail.com> wrote:
> On Fri, Jun 6, 2008 at 6:32 AM, Tomas Lindquist Olsen
> <tomas.l.olsen at gmail.com> wrote:
>> Hi all,
>>
>> I'm having some trouble with inline asm expressions, more specifically
>> how to create the right FunctionType for a given constraint set.
>> So far it has
2013 Jun 18
0
[LLVMdev] opt fails with assertion in Attributes.cpp
Hi Marcelo,
That should be fixed now at r184239. Sorry about the failure!
-bw
On Jun 17, 2013, at 6:16 AM, Marcelo Sousa <marceloabsousa at gmail.com> wrote:
> Hello,
>
> I'm getting an error when running opt with what seems to be a valid bytecode file compiled from one the Linux Kernel files.
> The error is:
> opt: /home/scratch/llvm/lib/IR/Attributes.cpp:119:
2009 Aug 19
1
[PATCH] drm/nouveau: Add a MM for mappable VRAM that isn't usable as scanout.
Dynamically resizing the framebuffer on nv04 was like playing Russian
roulette (and it often happened gratuitously) because it seems unable
to scan out from buffers above 16MB. This patch splits the mappable
VRAM into two chunks when that's the case, and makes the higher one to
be used as well when applicable.
Signed-off-by: Francisco Jerez <currojerez at riseup.net>
---