similar to: [LLVMdev] [PowerPC] ABI questions

Displaying 20 results from an estimated 1000 matches similar to: "[LLVMdev] [PowerPC] ABI questions"

2014 Jul 31
2
[LLVMdev] [PowerPC] ABI questions
----- Original Message ----- > From: "Ulrich Weigand" <Ulrich.Weigand at de.ibm.com> > To: "David Wiberg" <dwiberg at gmail.com> > Cc: llvmdev at cs.uiuc.edu > Sent: Wednesday, July 30, 2014 2:29:22 PM > Subject: Re: [LLVMdev] [PowerPC] ABI questions > > Hi David, > > > I'm trying to understand which ABIs are supported in the
2014 Jul 30
2
[LLVMdev] [PowerPC] ABI questions
Hello Ulrich, Thank you for a good explanation of the different variants. 2014-07-30 21:29 GMT+02:00 Ulrich Weigand <Ulrich.Weigand at de.ibm.com>: > Hi David, > >> I'm trying to understand which ABIs are supported in the PowerPC >> backend and I'm getting a bit confused. Here's what I've gathered so >> far alongside with some questions. > >
2014 Aug 01
3
[LLVMdev] [PowerPC] ABI questions
On 30 Jul 2014, at 21:29, Ulrich Weigand wrote: > The ELFv1 ABI is used on 64-bit big-endian Linux and AIX. There's one small difference between the two: with the 64 bit ELFv1/ SVR4 ABI, tail padding for structs passed by value is only performed in case the struct is larger than 8 bytes, while for AIX 64 bit it's always done. As an aside, on Darwin/ppc64 it's done if the
2015 Jul 08
2
[LLVMdev] The Trouble with Triples
> -----Original Message----- > From: Renato Golin [mailto:renato.golin at linaro.org] > Sent: 08 July 2015 16:09 > To: Daniel Sanders > Cc: LLVM Developers Mailing List (llvmdev at cs.uiuc.edu); Eric Christopher > (echristo at gmail.com); Jim Grosbach (grosbach at apple.com) > Subject: Re: The Trouble with Triples > > On 8 July 2015 at 15:31, Daniel Sanders
2017 Aug 22
2
Subtarget Initialization in <ARCH>TargetMachine constructor
Hi, I found some different discrepancy on how Subtarget is created between some arch specific TargetMachine constructor. For example, for BPF/Lanai: BPFTargetMachine::BPFTargetMachine(const Target &T, const Triple &TT, StringRef CPU, StringRef FS, const TargetOptions &Options,
2014 Sep 09
3
[PATCH] ppc64: ELFv2: Load TOC value in system call stub
This fixes a segmentation fault in the system call's error handling path with dynamically-linked binaries on PowerPC64 little endian. The system call stub wasn't loading up r2 with the appropriate TOC value in its global entry point. The r2 setup code comes from the FUNC_START macro in gcc [1] and an equivalent one can also be found in the LOCALENTRY macro in glibc [2]. On the ELFv2 ABI
2001 Oct 12
1
rsync binary for ncr mp ras svr4
hello everybody, Anybody ever compile rsync under "ncr mp ras svr4" unix system? I'm having some problem to run it. I compiled everything as in README file. when i tried run the rsync binary i received this error: ksh: rsync: not found unexpected EOF in read_timeout i even use full path to rsync and yer still get the same error. Anybody could help me, please? i really need this
2015 Apr 27
2
Real sh? Or other efficient shell for non-interactive scripts
<m.roth at 5-cent.us> wrote: > Ah. I don't remember if I was using csh, or ksh, and didn't realize about > bash. I *think* I vaguely remember that sh seemed to be more capable than > I remembered. If you like to check what the Bourne Shell did support in the late 1980s, I recommend you to fetch recent Schily tools from:
2002 Feb 25
2
samba & solaris 8
trying to compile 2.2.3a on solaris 8 and getting the following: Is it supported on sol 8? after typing configure and after many lines i get: -----much deleted------ ecking how to get filesystem space usage checking statvfs64 function (SVR4)... no checking statvfs function (SVR4)... no checking for 3-argument statfs function (DEC OSF/1)... no checking for two-argument statfs with statfs.bsize
2015 Apr 24
2
Real sh? Or other efficient shell for non-interactive scripts
On Fri, Apr 24, 2015 at 08:32:45AM -0400, Scott Robbins wrote: > Wasn't Solaris, which for awhile at least, was probably the most popular > Unix, using ksh by default? Solaris /bin/sh was a real real dumb version of the bourne shell. Solaris included /bin/ksh as part of the core distribution (ksh88 was a part of the SVr4 specification) and so many scripts were written with #!/bin/ksh at
2014 Jun 17
4
[LLVMdev] triples for baremetal
[+llvmdev, -llvm-dev] (Oopsies, llvmdev doesn't have a hyphen in it like all the others do) On 6/17/14, 10:45 AM, Jonathan Roelofs wrote: > [+llvm-dev, cfe-dev] > > Was "Re: [PATCH] ARM: allow inline atomics on Cortex M" > > On 6/17/14, 10:42 AM, Jonathan Roelofs wrote: >> >> >> On 6/17/14, 9:35 AM, Renato Golin wrote: >>> On 17 June 2014
2014 Jun 19
2
[LLVMdev] [PATCH] triples for baremetal
Eric, Attached are patches for llvm and clang that implement this. I've made 'none' a component that must be added explicitly (i.e. don't turn arm-eabi into arm--none-eabi, but rather turn it into arm--unknown-eabi) to try to reduce surprises. It also keeps the normalization logic a bit simpler than it would otherwise have to be. SPIR triples were one place where I was
2015 Jul 09
5
[LLVMdev] The Trouble with Triples
> -----Original Message----- > From: Renato Golin [mailto:renato.golin at linaro.org] > Sent: 08 July 2015 19:01 > To: Daniel Sanders > Cc: LLVM Developers Mailing List (llvmdev at cs.uiuc.edu); Eric Christopher > (echristo at gmail.com); Jim Grosbach (grosbach at apple.com) > Subject: Re: The Trouble with Triples > > On 8 July 2015 at 17:43, Daniel Sanders
2001 May 03
2
configure problem
Hi! I am trying to install samba 2.2 on a Sun and I'm getting this error: ./configure --prefix=/local --with-ssl checking how to get filesystem space usage checking statvfs64 function (SVR4)... no checking statvfs function (SVR4)... no checking for 3-argument statfs function (DEC OSF/1)... no checking for two-argument statfs with statfs.bsize member (AIX, 4.3BSD)... no checking for
1997 Oct 07
2
NT and slow logon
Hi, still got the problem of NT slow logon, what am I doing wrong? This is the situation: Samba running on Unixware 2.1.1, SVR4 and RedHad. Win95 and smbclient in any unix works fine. A win NT machine sees the workgroup, but browsing to it takes a LONG time ( 3 or 4 minutes or so..) and when the machines appear ( redhat, unixware and SVR4 ) it again takes a lot of time to log on, after that
2002 Aug 19
1
RPM build errors-Possible Bug?
Hello all. I'm trying to create the rpm for Samba 2.2.5. I haven't uninstalled the other version as we are using it. I got the tar.gz from the Samba web site. I type # sh makerpms.sh and this is what I get this @ the end: checking statvfs64 function (SVR4)... no checking statvfs function (SVR4)... no checking for 3-argument statfs function (DEC OSF/1)... no checking for two-argument
2012 Aug 03
2
[LLVMdev] Formats supported by llvm/Object/Archive.h
Hi, llvmdev I've tried to use llvm/Object/Archive.h to print the archive symbol table for standard Unix .a files by slightly extending a code in llvm-nm, and the code crashed with wild segfault. It looks like the implementation in lib/Object/Archive.cpp assumes completely different symbol table format from what I have (which I believe is SVR4/GNU variant). Which archive formats does libObject
2015 May 13
3
Bug#785187: Bug#785187: xen-hypervisor-4.5-amd64: Option ucode=scan is not working
> > according to the documentation the option ucode=scan should tell XEN to > > look for a microcode update in an uncompressed initrd. > > > > While I don?t use the Debian kernel the tools to generate the initrd are > > part of Debian. The command ?cpio -i < /boot/initrd.img-4.0.2-Dom0? > > creates the directory structure
2009 Jan 27
2
[LLVMdev] PPC calling convention -- how to provide an environment pointer?
> Message: 5 > Date: Mon, 26 Jan 2009 21:47:12 -0500 > From: "Jonathan S. Shapiro" <shap at eros-os.com> > Subject: [LLVMdev] PPC calling convention -- how to provide an > environment pointer? > To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > Message-ID: <1233024432.24380.11.camel at vmx> > Content-Type: text/plain > > This is
2012 Mar 23
2
[LLVMdev] Fixing VAARG on PPC64
The PowerPC backend on PPC64 for non-Darwin (SVR4 ABI) systems currently has a problem handling integer types smaller than 64 bits. This is because the ABI specifies that these types are zero-extended to 64 bits on the stack and the default logic provided in LegalizeDAG does not use that convention. Specifically, for these targets we have: setOperationAction(ISD::VAARG, MVT::Other, Expand);