search for: ccflag

...E) diff --git a/drivers/gpu/drm/amd/lib/Makefile b/drivers/gpu/drm/amd/lib/Makefile index 6902430..d534992 100644 --- a/drivers/gpu/drm/amd/lib/Makefile +++ b/drivers/gpu/drm/amd/lib/Makefile @@ -27,6 +27,6 @@ # driver components or later moved to kernel/lib for sharing with # other drivers. -ccflags-y := -I$(src)/../include +ccflags-y := -I $(srctree)/$(src)/../include obj-$(CONFIG_CHASH) += chash.o diff --git a/drivers/gpu/drm/arm/display/komeda/Makefile b/drivers/gpu/drm/arm/display/komeda/Makefile index 1b875e5..a72e30c 100644 --- a/drivers/gpu/drm/arm/display/komeda/Makefile +++ b/driv...

Hello, For my backend, I define and use a CC register similiarly to the EFLAGS register in X86 (I call it CCFLAGS). But if I make all arithmetic/logic instructions affect it ('let Defs = [CCFLAGS] in...' in InstrInfo.td) I run into // The only case we should have a dead physreg here without a killing or // instruction where we know it's dead is if it is live-in to the function // and never...

...E) diff --git a/drivers/gpu/drm/amd/lib/Makefile b/drivers/gpu/drm/amd/lib/Makefile index 6902430..d534992 100644 --- a/drivers/gpu/drm/amd/lib/Makefile +++ b/drivers/gpu/drm/amd/lib/Makefile @@ -27,6 +27,6 @@ # driver components or later moved to kernel/lib for sharing with # other drivers. -ccflags-y := -I$(src)/../include +ccflags-y := -I $(srctree)/$(src)/../include obj-$(CONFIG_CHASH) += chash.o diff --git a/drivers/gpu/drm/i915/gvt/Makefile b/drivers/gpu/drm/i915/gvt/Makefile index b016dc7..a4a5a96 100644 --- a/drivers/gpu/drm/i915/gvt/Makefile +++ b/drivers/gpu/drm/i915/gvt/Makefile...

A physical register cannot be live across the block. So it must have a use in the block or it must be marked dead. From your dump, it looks like the CCFLAGS defs are not being marked dead. It's unclear where things went wrong, but you can step through LiveVariables to debug this. Evan On Jan 9, 2009, at 2:50 AM, Christian Sayer wrote: > Hello, > > For my backend, I define and use a CC register similiarly to the > EFLAGS register...

...b/Makefile b/drivers/gpu/drm/amd/lib/Makefile > index 6902430..d534992 100644 > --- a/drivers/gpu/drm/amd/lib/Makefile > +++ b/drivers/gpu/drm/amd/lib/Makefile > @@ -27,6 +27,6 @@ > # driver components or later moved to kernel/lib for sharing with > # other drivers. > > -ccflags-y := -I$(src)/../include > +ccflags-y := -I $(srctree)/$(src)/../include > > obj-$(CONFIG_CHASH) += chash.o > diff --git a/drivers/gpu/drm/arm/display/komeda/Makefile b/drivers/gpu/drm/arm/display/komeda/Makefile > index 1b875e5..a72e30c 100644 > --- a/drivers/gpu/drm/arm/disp...

...lib/Makefile b/drivers/gpu/drm/amd/lib/Makefile > index 6902430..d534992 100644 > --- a/drivers/gpu/drm/amd/lib/Makefile > +++ b/drivers/gpu/drm/amd/lib/Makefile > @@ -27,6 +27,6 @@ > # driver components or later moved to kernel/lib for sharing with > # other drivers. > > -ccflags-y := -I$(src)/../include > +ccflags-y := -I $(srctree)/$(src)/../include > > obj-$(CONFIG_CHASH) += chash.o > diff --git a/drivers/gpu/drm/arm/display/komeda/Makefile b/drivers/gpu/drm/arm/display/komeda/Makefile > index 1b875e5..a72e30c 100644 > --- a/drivers/gpu/drm/arm/displa...

Evan, >A physical register cannot be live across the block. So it >must have a use in the block or it must be marked dead. From >your dump, it looks like the CCFLAGS defs are not being marked >dead. It's unclear where things went wrong, but you can step >through LiveVariables to debug this. Thanks for your response. I did quite some stepping through the llc passes, and it turned out what now looks fairly obvious: The instructions containing the CCFL...

...> ?# as published by the Free Software Foundation. > ? > +CFLAGS_virtio_ccw.o += -D__CHECK_ENDIAN__ > +CFLAGS_kvm_virtio.o += -D__CHECK_ENDIAN__ > ?s390-virtio-objs := virtio_ccw.o > ?ifdef CONFIG_S390_GUEST_OLD_TRANSPORT > ?s390-virtio-objs += kvm_virtio.o Here you could use ccflags-y += -D__CHECK_ENDIAN__ for example, or even subdir-ccflags-y += -D__CHECK_ENDIAN__ (in case any subdirs ever get added here) > --- a/drivers/vhost/Makefile > +++ b/drivers/vhost/Makefile > @@ -1,3 +1,4 @@ > +ccflags-y := -D__CHECK_ENDIAN__ Looks like you did that here and in some...

...> ?# as published by the Free Software Foundation. > ? > +CFLAGS_virtio_ccw.o += -D__CHECK_ENDIAN__ > +CFLAGS_kvm_virtio.o += -D__CHECK_ENDIAN__ > ?s390-virtio-objs := virtio_ccw.o > ?ifdef CONFIG_S390_GUEST_OLD_TRANSPORT > ?s390-virtio-objs += kvm_virtio.o Here you could use ccflags-y += -D__CHECK_ENDIAN__ for example, or even subdir-ccflags-y += -D__CHECK_ENDIAN__ (in case any subdirs ever get added here) > --- a/drivers/vhost/Makefile > +++ b/drivers/vhost/Makefile > @@ -1,3 +1,4 @@ > +ccflags-y := -D__CHECK_ENDIAN__ Looks like you did that here and in some...

I am wondering how to express physical register dependencies between instructions, typically in the case for conditionnal branch, where an instruction which sets the condition codes is followed by a conditionnal branch. Assuming CCFLAGS is defined in my registerInfo.td, and that I am using llvm-2.5 release, it seems several items need to be set in the .td file : 1 - SDNPOptInFlag / SDNPOptOutFlag 2 - Defs = [CCFLAGS] / Uses = [CCFLAGS] 3 - (implicit CCFLAGS) 4 - explicit usage of CCFLAGS As a new comer to LLVM, I am missing the...

...nly seems to affect some users. Hopefully this harmless oneliner is acceptable. drm/nouveau/Kbuild | 1 + 1 file changed, 1 insertion(+) diff --git a/drm/nouveau/Kbuild b/drm/nouveau/Kbuild index fde6e3656636..c64b000a9ee6 100644 --- a/drm/nouveau/Kbuild +++ b/drm/nouveau/Kbuild @@ -1,4 +1,5 @@ ccflags-y := -Iinclude/drm +ccflags-y += -Iinclude/uapi/drm ccflags-y += -I$(src)/include ccflags-y += -I$(src)/include/nvkm ccflags-y += -I$(src)/nvkm -- 2.10.2

...LINCL = /usr/src/kernel-headers-`uname -r`/include #KRNLINCL = /lib/modules/`uname -r`/build/include #KRNLINCL = /usr/src/linux/include And modify the lines as thus - DEFINES = -DMODULE -D__KERNEL__ -DNDEBUG \ -D__$(CARD)__ -DTARGET=\"$(CARD)\" CCFLAGS = -c $(DEFINES) -O2 -Wall -I $(KRNLINCL) With - DEFINES = -DMODULE -DMODVERSIONS -D__KERNEL__ -DNDEBUG \ -D__$(CARD)__ -DTARGET=\"$(CARD)\" CCFLAGS = -c $(DEFINES) -march=i686 -O2 -Wall -I $(KRNLINCL) \ -include $(KRNLINCL)/linux/modversions.h Agai...

...s that in the end become a compare // and a cmov_logical { MachineOperand Dst = MI->getOperand(0); MachineOperand TrueVal = MI->getOperand(1); MachineOperand FalseVal = MI->getOperand(2); MachineOperand CCFlag = MI->getOperand(3); CC = (INSTCC::CondCodes)MI->getOperand(3).getImm(); // Here I want to get the destination register of SET_CC instruction and place it as the first addReg TODO(Get setcc destination register); BuildMI(BB, TII.get(INST::CMO...

...M_MXC_RNGA) += mxc-rnga.o diff --git a/drivers/gpu/drm/virtio/Makefile b/drivers/gpu/drm/virtio/Makefile index 3fb8eac..1162366 100644 --- a/drivers/gpu/drm/virtio/Makefile +++ b/drivers/gpu/drm/virtio/Makefile @@ -3,6 +3,7 @@ # Direct Rendering Infrastructure (DRI) in XFree86 4.1.0 and higher. ccflags-y := -Iinclude/drm +ccflags-y += -D__CHECK_ENDIAN__ virtio-gpu-y := virtgpu_drv.o virtgpu_kms.o virtgpu_drm_bus.o virtgpu_gem.o \ virtgpu_fb.o virtgpu_display.o virtgpu_vq.o virtgpu_ttm.o \ diff --git a/drivers/net/Makefile b/drivers/net/Makefile index 7336cbd..3f587de 100644 --- a/drivers/ne...

...annot create execu tables See `config.log' for more details. make: *** No rule to make target `clean'. Stop. make: *** No rule to make target `opt'. Stop. for x in wrapper asterisk-driver; do make -C $x build || exit 1 ; done make: *** No rule to make target `ccflags'. Stop. make: *** No rule to make target `ccflags'. Stop. make[1]: Entering directory `/usr/src/asterisk-oh323-0.6.5/wrapper' ./check_ver /usr/src/pwlib pwlib ./check_ver /usr/src/openh323 openh323 g++ -Wall -x c++ -Os -DWRAPTRACING -DWRAPTRACING_LEVEL=5 -DPWLIBVERSION=\"1.6.6...

...some shared libraries of AIX does not work at the same time. I tried to configure & make with the following environment vars CC=xlc F77=xlf CCC=xlC CFLAGS=-O3 -qstrict -qmaxmem=8192 FFLAGS=-O3 -qstrict -qmaxmem=8192 MAIN_LDFLAGS=-Wl,-brtl SHLIB_LDFLAGS=-Wl,-G CXXFLAGS=-O2 -qmaxmem=8192 FC=xlf CCFLAGS=-O3 -qstrict -qmaxmem=8192 But for some reason at make the compilation failed when trying to locate a shared library for X. For this reason I tried to discard shared libraries enabling --disable-shared on configure, but this didn't help (Nor removing MAIN_LDFLAGS and SHLIB_LDFLAGS). Next I t...

.../arm64/kernel/vdso/Makefile b/arch/arm64/kernel/vdso/Makefile index 45d5cfe46429..60df97f2e7de 100644 --- a/arch/arm64/kernel/vdso/Makefile +++ b/arch/arm64/kernel/vdso/Makefile @@ -28,7 +28,7 @@ ldflags-y := -shared -nostdlib -soname=linux-vdso.so.1 --hash-style=sysv \ $(btildflags-y) -T ccflags-y := -fno-common -fno-builtin -fno-stack-protector -ffixed-x18 -ccflags-y += -DDISABLE_BRANCH_PROFILING +ccflags-y += -DDISABLE_BRANCH_PROFILING -DBUILD_VDSO CFLAGS_REMOVE_vgettimeofday.o = $(CC_FLAGS_FTRACE) -Os $(CC_FLAGS_SCS) $(GCC_PLUGINS_CFLAGS) KBUILD_CFLAGS += $(DISABLE_LTO) diff --gi...

.../arm64/kernel/vdso/Makefile b/arch/arm64/kernel/vdso/Makefile index 45d5cfe46429..60df97f2e7de 100644 --- a/arch/arm64/kernel/vdso/Makefile +++ b/arch/arm64/kernel/vdso/Makefile @@ -28,7 +28,7 @@ ldflags-y := -shared -nostdlib -soname=linux-vdso.so.1 --hash-style=sysv \ $(btildflags-y) -T ccflags-y := -fno-common -fno-builtin -fno-stack-protector -ffixed-x18 -ccflags-y += -DDISABLE_BRANCH_PROFILING +ccflags-y += -DDISABLE_BRANCH_PROFILING -DBUILD_VDSO CFLAGS_REMOVE_vgettimeofday.o = $(CC_FLAGS_FTRACE) -Os $(CC_FLAGS_SCS) $(GCC_PLUGINS_CFLAGS) KBUILD_CFLAGS += $(DISABLE_LTO) diff --gi...

...g working OK. I've also tried with/without patching oh323 with supplied patch. Any hint, advice ? Thanks in advance, regards, Rob. centrala:~/Asterisk/h323/asterisk-oh323-0.6.5 # make for x in wrapper asterisk-driver; do make -C $x build || exit 1 ; done make: *** No rule to make target `ccflags'. Stop. make: *** No rule to make target `ccflags'. Stop. make[1]: Entering directory `/root/Asterisk/h323/asterisk-oh323-0.6.5/wrapper' ./check_ver /root/Asterisk/h323/pwlib pwlib ./check_ver /root/Asterisk/h323/openh323 openh323 g++ -Wall -x c++ -Os -DWRAPTRACING -DWRAPTRACING_LEV...

...l builds, which are currently overwhelmingly riddled with > niggly little warnings. The next question is, how do we keep it W=1 clean going forward? Most people don't use W=1 because it's too noisy, so it's a bit of a catch-22. In i915, we enable a lot of W=1 warnings using subdir-ccflags-y in our Makefile. For CI/developer use we also enable kernel-doc warnings by default. Should we start enabling some of those warning flags in drm/Makefile to to keep the entire subsystem warning free? BR, Jani. -- Jani Nikula, Intel Open Source Graphics Center