search for: warnflags

...-12,6 +12,9 @@ endif ifeq ($(ARCH),x86_64) GCCOPT += $(call gcc_ok,-m64,) +ifeq ($(FWCLASS),EFI) + GCCOPT += $(call gcc_ok,-mno-red-zone) +endif #let preferred-stack-boundary be default(=4) MARCH = x86-64 endif @@ -54,9 +57,7 @@ CFLAGS = $(OPTFLAGS) $(REQFLAGS) $(WARNFLAGS) $(LIBFLAGS) -ifeq ($(FWCLASS),EFI) -CFLAGS += -mno-red-zone -else +ifneq ($(FWCLASS),EFI) CFLAGS += -mregparm=3 -DREGPARM=3 endif

...inux-3.07/com32/lib/MCONFIG 2005-03-07 11:28:59.000000000 -0500 @@ -18,7 +18,7 @@ REQFLAGS = -g -m32 -mregparm=3 -DREGPARM=3 -D__COM32__ -I. -I./sys -I../include OPTFLAGS = -Os -march=i386 -falign-functions=0 -falign-jumps=0 \ - -falign-labels=0 + -falign-labels=0 -finline-limit=1000 WARNFLAGS = -W -Wall -Wpointer-arith -Wwrite-strings -Wstrict-prototypes -Winline CFLAGS = -Wp,-MT,$@,-MD,$(dir $@).$(notdir $@).d $(OPTFLAGS) \ --- syslinux-3.07/com32/lib/libgcc/__moddi3.c.gcc4 2004-11-17 02:19:58.000000000 -0500 +++ syslinux-3.07/com32/lib/libgcc/__moddi3.c 2005-03-07 11:26:46.0000000...

From: Sylvain Gault <sylvain.gault at gmail.com> The System V ABI for x86-64 specify that a "red zone" is an area of 128 bytes above the current stack frame. This area can be used by a called function in order to avoid the overhead of modifying the stack pointer. The direct effect is that interrupt/event/signal handlers must not write to this area. In the UEFI calling convention,

Hi Ady, Would it work if we removed "ifdef EFI_BUILD" condition and just add -mno-red-zone for all x86_64 builds? If not, do you have any ideas how to pass this flag? This could work, because the patch is adding the -mno-red-zone flag only for x86_64 builds, which are only used in the form of the efi64 target. The efi32 and bios targets are both 32-bit. BTW. I also tried 6.04-pre1 and

...9;t available in the # fixed-point versions. It's OK, because we have to have a non-graphical # fallback anyway, just use that on old machines... @@ -52,13 +77,37 @@ OPTFLAGS = -Os -march=$(MARCH) -falign-functions=0 -falign-jumps=0 \ -falign-labels=0 -ffast-math -fomit-frame-pointer WARNFLAGS = $(GCCWARN) -Wpointer-arith -Wwrite-strings -Wstrict-prototypes -Winline -CFLAGS = $(OPTFLAGS) $(REQFLAGS) $(WARNFLAGS) $(LIBFLAGS) +CFLAGS = $(OPTFLAGS) $(REQFLAGS) $(WARNFLAGS) $(LIBFLAGS) $(FWFLAGS) ifndef EFI_BUILD CFLAGS += -mregparm=3 -DREGPARM=3 endif VPATH = $(SRC) + +LIBSYS_OB...

From: Matt Fleming <matt.fleming at intel.com> The following patch series is available at, git://git.zytor.com/users/mfleming/syslinux.git elflink All patches are against the 'elflink' branch. This series fixes a few serious bugs and some behavioural incompatibilities with the 4.x series. Matt Fleming (19): ldlinux: Initialise 'p' before using it. ldlinux: Parse

Hi, These patches contain support for some features that are already in Syslinux 4 but weren't working properly on the elflink branch. It's another step closer to feature parity with Syslinux 4. Having to jump through the comboot API for localboot support is less than ideal and I'll eventually fix that, probably when we move a big chunk of code from asm to C. Also, there's a

From: Matt Fleming <matt.fleming at linux.intel.com> This series fixes some bugs and switches the elflink branch to be entirely ELF modules. It applies on top of, http://syslinux.zytor.com/archives/2011-April/016369.html The deletions in the diff stat below are mainly from deleting com32/elflink/modules (finally!). Now there should be no duplicate code because we don't need COM32 and