Displaying 20 results from an estimated 1000 matches similar to: "[LLVMdev] Extended Inline asm with double data type crashes clang"
2012 Nov 20
0
[LLVMdev] Extended Inline asm with double data type crashes clang
I reported http://llvm.org/pr14393 to track it.
On 20 November 2012 05:18, rajesh viswabramana
<viswabramana.rajesh at gmail.com> wrote:
> Hi,
>
> Clang crashes when below snippet of code is compiled (used latest svn
> version)
>
> double func1()
> {
> double x ;
> asm ( "" : "=r"(x) : "0"(x) );
> return x;
> }
>
2012 Nov 21
2
[LLVMdev] Extended Inline asm with double data type crashes clang
Thanks Rafael,
Hello All,
Could anyone please comment, which part in selectiondag need to be
understood/modified to fix this.
Regards,
Rajesh
On Wed, Nov 21, 2012 at 2:38 AM, Rafael Espíndola <
rafael.espindola at gmail.com> wrote:
> I reported http://llvm.org/pr14393 to track it.
>
> On 20 November 2012 05:18, rajesh viswabramana
> <viswabramana.rajesh at
2012 Nov 22
0
[LLVMdev] Extended Inline asm with double data type crashes clang
Hi all,
I tried same code on gcc for arm(hard float),
double f2 ()
{
double x = 10.0;
asm ("" : "=r" (x) : "0" (x));
return x;
}
> arm-linux-gnueabi-gcc -S -mhard-float pr39058.c -O2
Generates proper code,
mov r3, #0
mov r2, #0
movt r3, 16420
fmdrr d0, r2, r3
bx lr
But llvm crashes, If data type is "double",
2012 Dec 19
2
[LLVMdev] Function inline causes crash in clang for .ast to .s
Hi,
Clang crashes when tried to compile from .ast to .s for below sample code,
inline-test.c
**
*extern inline int func1 (void) { return 0; }
inline int func1 (void) { return 1; }*
clang *works fine* for .c -> .s,
*>clang inline-test.c -std=c99 -fgnu89-inline -S -o inline-test.s *
But *crashes* when tried to generate .s from .ast for same file,
*>clang inline-test.c -std=c99
2015 Apr 21
3
[LLVMdev] libclang_rt.asan-x86_64.a: No such file or directory
I just tried building the latest clang following the instructions in
http://clang.llvm.org/get_started.html, and got this error when trying to
compile at test program:
/usr/bin/ld: cannot find /home/davem/clang-235334/bin/../lib/clang/3.7.0/lib/linux/libclang_rt.asan-x86_64.a: No such file or directory
This thread:
http://lists.cs.uiuc.edu/pipermail/llvmdev/2015-April/084175.html
indicates
2012 Dec 28
0
[LLVMdev] Function inline causes crash in clang for .ast to .s
Hi,
Could anyone please comment on this ?
Regards,
Rajesh
On Wed, Dec 19, 2012 at 6:54 PM, rajesh viswabramana <
viswabramana.rajesh at gmail.com> wrote:
> Hi,
>
> Clang crashes when tried to compile from .ast to .s for below sample code,
>
> inline-test.c
> **
> *extern inline int func1 (void) { return 0; }
> inline int func1 (void) { return 1; }*
>
>
2009 Feb 11
0
[LLVMdev] Bug in SelectionDAGBuild.cpp?
I'm hitting a problem in SelectionDAGBuild::visitRet(), mainly:
MVT VT = ValueVTs[j];
// FIXME: C calling convention requires the return type to be promoted
to
// at least 32-bit. But this is not necessary for non-C calling
// conventions.
if (VT.isInteger()) {
MVT MinVT = TLI.getRegisterType(MVT::i32);
if (VT.bitsLT(MinVT))
VT = MinVT;
2013 Jun 19
2
[LLVMdev] ARM struct byval size > 64 triggers failure
I missed that the testing case is returning a struct.
You are right in VARegSaveSize.
For callee:
sub sp, sp, #16
push {r11, lr}
mov r11, sp
sub sp, sp, #8
str r3, [r11, #20]
str r2, [r11, #16]
str r1, [r11, #12]
ldr r1, [r11, #76]
The beginning of the input struct @ sp_at_entry - 16 - 8 + 12 = sp_at_entry -12
# of leftover bytes 67-12 = 55
r11+76 is @ sp_at_entry - 24 + 76 = sp_at_entry
2013 Jun 20
1
[LLVMdev] ARM struct byval size > 64 triggers failure
> - "since ABI says the stack pointer needs to be 8 byte aligned at function entry point" (taken from Manman's reply)
> What will be considered as entry point here?
> Is it place of SP Adjustments "sub sp, sp, #16"
> (Or) Is it place of first user instruction(end of prologue) "ldr r2, .LCPI0_0"
Eight byte stack alignment is a
2013 Jun 18
3
[LLVMdev] ARM struct byval size > 64 triggers failure
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130618/5b2a15e3/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 201306181656803_BEI0XT4N.gif
Type: image/gif
Size: 14036 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130618/5b2a15e3/attachment.gif>
2013 Jun 18
0
[LLVMdev] ARM struct byval size > 64 triggers failure
Hi Rajesh,
The callee code looks okay to me
> Assembly for check114
> ---------------------------------------------------------------
> sub sp, sp, #16
> push {r11, lr}
> mov r11, sp
> sub sp, sp, #8
> str r3, [r11, #20]
> str r2, [r11, #16]
> str r1, [r11, #12]
> ldr r1,
2013 Sep 09
0
[LLVMdev] Intel Memory Protection Extensions (and types question)
Hi Kevin,
Thanks for working on this. We usually try really hard to avoid adding new types such as x86mmx. I don’t know the memory-protection instruction set at all but I imagine that you are not expecting other LLVM optimizations to interact with them right ? (it looks that way from this example[1]). If you are not accessing the individual components then you can use i128, or even <2 x
2010 Dec 29
2
[LLVMdev] stack alignment restriction
Hi
Is there a way to enforce a different alignment on vales on stack
as compared to other basic types. Particularly, i would like
characters to be stored at 2 byte boundary.
thanks
dz
2012 Dec 06
0
[LLVMdev] [PATCH] Replacing EVT:s with MVT:s (when possible)
Here is a series of patches replacing EVT with MVT at a number of places in TargetLowering. The last two patches are related cleanups in SelectionDAGBuilder.
/Patrik Hägglund
> git log --stat --reverse origin/master..
commit 8dabe3eb005360347eabb86a2e88c3b6e9098ed5
Author: Patrik Hägglund <patrik.h.hagglund at ericsson.com>
Date: Tue Dec 4 10:37:37 2012 +0100
Change
2013 Sep 09
2
[LLVMdev] Intel Memory Protection Extensions (and types question)
Hi,
On Monday, September 09, 2013 4:20 PM, Nadav Rotem [mailto:nrotem at apple.com] wrote:
> Thanks for working on this. We usually try really hard to avoid adding new
> types such as x86mmx. I don't know the memory-protection instruction set at
> all but I imagine that you are not expecting other LLVM optimizations to
> interact with them right ? (it looks that way from this
2016 Oct 02
2
[PATCH] nv50/ir: Propagate third immediate src when folding OP_MAD
Previously we'd end up with an unnecessary mov for the thirs immediate value.
total instructions in shared programs : 851881 -> 851864 (-0.00%)
total gprs used in shared programs : 110295 -> 110295 (0.00%)
total local used in shared programs : 1020 -> 1020 (0.00%)
local gpr inst bytes
helped 0 0 17 17
2009 Apr 07
0
[LLVMdev] Porting to System z
Hi,
> llvm[1]: Building Intrinsics.gen.tmp from Intrinsics.td
> tblgen: IntrinsicEmitter.cpp:163: void EmitTypeForValueType(std::ostream&,
> llvm::MVT::SimpleValueType): Assertion `false && "Unsupported ValueType!"'
> failed.
this came up before IIRC, but I don't remember the details - buggy system
compiler? Try searching the archives. Also, if you
2009 Apr 07
2
[LLVMdev] Porting to System z
Hi,
I am beginning the porting process for Linux on System z (aka IBM
Mainframe). I thought I¹d build LLVM first with the c and cpp backends so
that tools like TableGen would be created that I¹d then use to process the
.td files that I¹ll be creating. So I used svn to grab the code from the
repository and ran configure and make. However, the build breaks at this
point:
llvm[1]: Building
2003 Aug 12
4
rsync problem
Hi all,
I've installed rsync-2.5.6 on a sun box (solaris 8). When I run rsync using the
command
rsync -a ssh /opt/local/pkgs/httpd/htdocs/ root@remotemachine:/mnt/
I get the error
rsync: connection unexpectedly closed (0 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(165)
What could be the reason? Any help would be appreciated.
Thanks,
Rajesh.
2012 Aug 20
5
automatically detaching PCI host devices from guest for SRIOV usage.
Dear List ,
We are using intel 82599EB based SRIOV capable 10GbE cards
on the host machine.The VFs are being assigned to the guest
in pass through mode and are providing the network connectivity
as expected.
However when we shutdown the guest the connectivity does not
comes back via the VFs on the guest in next boot unless
the VFs are detached from the *guest* *before* initiating a
shutdown of