similar to: [LLVMdev] [RFC] Encoding Compile Flags into the IR

On Apr 30, 2012, at 1:00 PM, dag at cray.com wrote: > Bill Wendling <wendling at apple.com> writes: > >> Link-Time Optimization has a problem. We need to preserve some of the >> flags with which the modules were compiled so that the semantics of >> the resulting program are correct. For example, a module compiled with >> `-msoft-float' should use library

On 29 April 2012 18:44, Bill Wendling <wendling at apple.com> wrote: > Hi, > > Link-Time Optimization has a problem. We need to preserve some of the flags with which the modules were compiled so that the semantics of the resulting program are correct. For example, a module compiled with `-msoft-float' should use library calls for floating point. And that's only the tip of

On Apr 30, 2012, at 4:12 PM, Bill Wendling wrote: > On Apr 30, 2012, at 1:00 PM, dag at cray.com wrote: > >> Bill Wendling <wendling at apple.com> writes: >> >>> Link-Time Optimization has a problem. We need to preserve some of the >>> flags with which the modules were compiled so that the semantics of >>> the resulting program are correct. For

On 29 April 2012 23:44, Bill Wendling <wendling at apple.com> wrote: > Hi, > > Link-Time Optimization has a problem. We need to preserve some of the flags with which the modules were compiled so that the semantics of the resulting program are correct. For example, a module compiled with `-msoft-float' should use library calls for floating point. And that's only the tip of

Bill Wendling <wendling at apple.com> writes: > Link-Time Optimization has a problem. We need to preserve some of the > flags with which the modules were compiled so that the semantics of > the resulting program are correct. For example, a module compiled with > `-msoft-float' should use library calls for floating point. And that's > only the tip of the proverbial

On Apr 30, 2012, at 1:03 AM, Renato Golin wrote: > On 29 April 2012 23:44, Bill Wendling <wendling at apple.com> wrote: >> Hi, >> >> Link-Time Optimization has a problem. We need to preserve some of the flags with which the modules were compiled so that the semantics of the resulting program are correct. For example, a module compiled with `-msoft-float' should use

On Apr 29, 2012, at 5:39 PM, Rafael Espíndola wrote: > On 29 April 2012 18:44, Bill Wendling <wendling at apple.com> wrote: >> Hi, >> >> Link-Time Optimization has a problem. We need to preserve some of the flags with which the modules were compiled so that the semantics of the resulting program are correct. For example, a module compiled with `-msoft-float' should

Hello When i try to make world (any) from xen-3.0.2 to xen-unstable-src I gat following error : gcc -O2 -fomit-frame-pointer -DNDEBUG -m64 -Wall -Wstrict-prototypes -Wdeclaration-after-statement -nostdinc -fno-builtin -fno-common -fno-strict-aliasing -iwithprefix include -Werror -Wno-pointer-arith -pipe -I/home/test1/xen-unstable/xen/include

Hi Andrea, That is because the LR is the fixed register as per the http://infocenter.arm.com/help/topic/com.arm.doc.ihi0042e/IHI0042E_aapcs.pdf and out_char() function is not the leaf function ,Hence compiler tends to save and restore the LR and the save and restore of register r11 is to align stack for 8 bytes as per ARM EABI. Thanks ~Umesh On Tuesday, October 15, 2013, Umesh Kalappa

Package: xen Version: 4.1.0-3 Severity: important Tags: wheezy sid User: debian-gcc at lists.debian.org Usertags: ftbfs-gcc-4.6 ftbfs-werror This package builds with -Werror, and GCC 4.6 triggers new warnings which will make the package fail to build. Currently a Debian patch just passes -Wno-error=unused-but-set-variable and -Wno-error=unused-but-set-parameter to avoid build failures,

Hi, I am trying to compile the version on rhel 5.x box. Nasm version 0.98.39 I extracted the tar.gz and ran make in the extracted directory. Here is where it stops. gcc -Wp,-MT,rawcon.o,-MD,./.rawcon.o.d -m32 -ffreestanding -fno-stack-protector -fwrapv -freg-struct-return -march=i386 -Os -fomit-frame-pointer -mregparm=3 -DREGPARM=3 -msoft-float -fno-exceptions -fno-asynchronous-unwind-tables

Package: xen Version: 4.6.0-1+nmu2 Severity: serious This package fails to build in unstable: > sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux ... > mkdir -p compat > grep -v 'DEFINE_XEN_GUEST_HANDLE(long)' public/grant_table.h | \ > python /<<PKGBUILDDIR>>/debian/build/build-hypervisor_amd64_amd64/xen/tools/compat-build-source.py

Module-Level Attributes Overview -------- LLVM currently lacks the ability to specify an attribute on a module as a whole. This isn't typically a problem as most optimizations and code transformations rely upon more finer-grained information, such as function attributes. However, some transformations, in particular LTO, may need to know information about the module. As a side-benefit, it

make[1]: Entering directory `/syslinux-4.02-6-ge841d69/dos' gcc -Wp,-MT,syslxopt.o,-MD,./.syslxopt.o.d -m32 -ffreestanding -fno-stack-protector -fwrapv -freg-struct-return -march=i386 -Os -fomit-frame-pointer -mregparm=3 -DREGPARM=3 -msoft-float -fno-exceptions -fno-asynchronous-unwind-tables -fno-strict-aliasing -falign-functions=0 -falign-jumps=0 -falign-labels=0 -falign-loops=0

Hi List- I''m brand new to xen but an old hand with Linux. With a fresh, clean, Gentoo installation on this box, I''m attempting to install xen using the gentoo-standard: emerge xen but the process is failing with an error that''s very similar to one reported by another user (A Streetcar Named: see

gcc -O2 -fomit-frame-pointer -m32 -march=i686 -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement -D__XEN_TOOLS__ -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -mno-tls-direct-seg-refs -Werror -fno-stack-protector -fno-builtin -msoft-float -I../../../tools/include -I. -c -o hvmloader.o hvmloader.c cc1: warnings being treated as errors

Umesh, Makes some sort of sense to me, OTOH: If instead of choosing r11 as a "dummy" to align the stack we had chosen some other register in the range r0-r7 then we could have emitted the PUSH encoding T1 (2 bytes opcode) as opposed to the encoding T2 (which is a 4 bytes opcode). A On Tue, Oct 15, 2013 at 2:59 AM, Umesh Kalappa <umesh.kalappa0 at gmail.com>wrote: > Hi

I do recieve this error when building xen-unstable tree. gcc -O2 -fomit-frame-pointer -m32 -march=i686 -DNDEBUG -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement -DVMXASSIST -nostdinc -fno-builtin -fno-common -iwithprefix include -Werror -Wno-pointer-arith -pipe -I/home/xen-unstable.hg/xen/include

Hi, I have successfully installed Xen unstable binary on SuSE 9.3. I am trying to do a source install and I got the following error. Will be glad for any help or guidance. In file included from include/asm-xen/asm/processor.h:18, from include/asm/thread_info.h:17, from include/linux/thread_info.h:21, from include/linux/spinlock.h:12, from include/linux/capability.h:45, from

Thank you for your reply Eli, I too was working with Carey on this feature, so please let me reply. On 12/21/18 8:05 PM, Friedman, Eli via llvm-dev wrote: > As a side-note, you might want to check that prologue/epilogue emission won't emit a PUSH/POP that refers to a register reserved this way; we sometimes add an "extra" register to align the stack. Yes, you are right.