[src/trunk]: src/crypto/external/bsd/heimdal/lib/libasn1 Add hack for profili...

[christos <christos%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/4500170a6ecc
branches:  trunk
changeset: 821617:4500170a6ecc
user:      christos <christos%NetBSD.org@localhost>
date:      Sat Feb 11 04:56:37 2017 +0000

description:
Add hack for profiling bimodal label generation with -m32 on sparc64

diffstat:

 crypto/external/bsd/heimdal/lib/libasn1/Makefile |  13 ++++++++++++-
 1 files changed, 12 insertions(+), 1 deletions(-)

diffs (29 lines):

diff -r 91317bc3ed85 -r 4500170a6ecc crypto/external/bsd/heimdal/lib/libasn1/Makefile
--- a/crypto/external/bsd/heimdal/lib/libasn1/Makefile  Sat Feb 11 04:19:25 2017 +0000
+++ b/crypto/external/bsd/heimdal/lib/libasn1/Makefile  Sat Feb 11 04:56:37 2017 +0000
@@ -1,4 +1,4 @@
-# $NetBSD: Makefile,v 1.3 2017/01/28 21:31:51 christos Exp $
+# $NetBSD: Makefile,v 1.4 2017/02/11 04:56:37 christos Exp $
 
 USE_FORT?= yes # network protocol library
 
@@ -68,8 +68,19 @@
 SUBDIR=        asn1_compile
 .endif
 
+
 .include <${HEIMBASE}/Makefile.rules.inc>
 .include <bsd.lib.mk>
 .if ${USETOOLS} != "yes"
 .include <bsd.subdir.mk>
 .endif
+
+.if ${MACHINE_ARCH} == "sparc64"
+# Or anything else that uses PROFILE_HOOK with gcc.
+# What happens is that we end up generating one of two different
+# function orders and since the profile code uses the function
+# number for label generation, we end up with one of two different
+# label orders. Disabling ASLR or optimization fixes it.
+# This happens only with -m32...
+COPTS.asn1_krb5_asn1.c+=-O0
+.endif