Generate .op pattern rules for profiling builds only

.op pattern rules are not used in non-profiling builds.

This does not cause any changes to both profiling and non-profiling
builds.
This commit is contained in:
Florian Weimer 2016-09-21 10:45:19 +02:00
parent 1d2ea31ca9
commit 612148c660
2 changed files with 8 additions and 1 deletions

View File

@ -1,3 +1,8 @@
2016-09-21 Florian Weimer <fweimer@redhat.com>
* Makeconfig (all-object-suffixes): Include .op only if
$(build-profile).
2016-09-21 Florian Weimer <fweimer@redhat.com>
* elf/sln.c: Remove HAVE_CONFIG_H, S_ISDIR, S_ISLNK preprocessor

View File

@ -905,7 +905,8 @@ endif
# The compilation rules use $(CPPFLAGS-${SUFFIX}) and $(CFLAGS-${SUFFIX})
# to pass different flags for each flavor.
libtypes = $(foreach o,$(object-suffixes-for-libc),$(libtype$o))
all-object-suffixes := .o .os .op .oS
# .op may be added to all-object-suffixes below.
all-object-suffixes := .o .os .oS
object-suffixes :=
CPPFLAGS-.o = $(pic-default)
CFLAGS-.o = $(filter %frame-pointer,$(+cflags))
@ -930,6 +931,7 @@ PIE-ccflag = -fPIE
ifeq (yes,$(build-profile))
# Under --enable-profile, we will build a static library of profiled objects.
# The profiled object files are named foo.op.
all-object-suffixes += .op
object-suffixes += .op
CPPFLAGS-.op = -DPROF $(pic-default)
CFLAGS-.op = -pg