Searched refs:guard (Results 1 – 4 of 4) sorted by relevance
111 $(guard) $(LD_LTO) -r -o $@ $(filter-out %/efi/built_in.o,$^)118 $(guard) $(LD) $(LDFLAGS) -r -o $@ $^124 $(guard) $(LD) $(LDFLAGS) -r -o $@ $(filter-out %/efi/built_in.o,$^)172 $(TARGET).efi: guard = $(if $(shell echo efi/dis* | grep disabled),:) macro191 $(guard) $(NM) -pa --format=sysv $(@D)/.$(@F).$(VIRT_BASE).0 \193 $(guard) $(MAKE) -f $(BASEDIR)/Rules.mk $(@D)/.$(@F).0r.o $(@D)/.$(@F).0s.o195 $(guard) $(LD) $(call EFI_LDFLAGS,$(base)) -T efi.lds -N $< \198 $(guard) $(NM) -pa --format=sysv $(@D)/.$(@F).$(VIRT_BASE).1 \200 $(guard) $(MAKE) -f $(BASEDIR)/Rules.mk $(@D)/.$(@F).1r.o $(@D)/.$(@F).1s.o201 $(guard) $(LD) $(call EFI_LDFLAGS,$(VIRT_BASE)) -T efi.lds -N $< \[all …]
5476 static void __memguard_change_range(void *p, unsigned long l, int guard) in __memguard_change_range() argument5486 if ( guard ) in __memguard_change_range()
881 To guard against that we must be prepared to do patching similar to940 The old code allows much more flexibility and an additional guard,
332 /* The OS might guarantee only one guard page at the bottom of the stack,
Completed in 17 milliseconds