Module Name: src
Committed By: rin
Date: Mon Aug 10 06:46:27 UTC 2020
Modified Files:
src/doc: HACKS
Log Message:
Add hacks for GCC8 vs m68k ports:
compile aes_ccm_tag() with -O0 for GCC8
http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/crypto/aes/aes_ccm.c#rev1.5
compile kernel with -fno-omit-frame-pointer for GCC8
http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/arch/sun2/conf/Makefile.sun2#rev1.25
To generate a diff of this commit:
cvs rdiff -u -r1.207 -r1.208 src/doc/HACKS
Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.
Modified files:
Index: src/doc/HACKS
diff -u src/doc/HACKS:1.207 src/doc/HACKS:1.208
--- src/doc/HACKS:1.207 Sun May 10 06:38:24 2020
+++ src/doc/HACKS Mon Aug 10 06:46:27 2020
@@ -1,4 +1,4 @@
-# $NetBSD: HACKS,v 1.207 2020/05/10 06:38:24 maxv Exp $
+# $NetBSD: HACKS,v 1.208 2020/08/10 06:46:27 rin Exp $
#
# This file is intended to document workarounds for currently unsolved
# (mostly) compiler bugs.
@@ -975,3 +975,29 @@ descr GCC 8.4 miscompiles dwarf2expr.c w
only for earmv7hf{,eb} as far as I can see. Neither earmv6hf{,eb} nor
earmv7{,eb} (softfloat) are affected.
kcah
+
+port m68k
+hack compile aes_ccm_tag() with -O0 for GCC8
+cdate Mon Aug 10 06:27:29 UTC 2020
+who rin
+file src/sys/crypto/aes/aes_ccm.c: 1.5
+descr GCC 8.4 miscompiles aes_ccm_tag() for m68k with optimization level
+ -O[12], which results in failure in aes_ccm_selftest().
+ This is observed for amiga (A1200, 68060), mac68k (Quadra 840AV,
+ 68040), and luna68k (nono, 68030 emulator). However, it is not for
+ sun3 (TME, 68020 emulator) and sun2 (TME, 68010 emulator).
+ At the moment, it is unclear whether this is due to differences b/w
+ 68010-20 vs 68030-60, or something wrong with TME.
+kcah
+
+port sun2
+hack compile kernel with -fno-omit-frame-pointer for GCC8
+cdate Mon Aug 10 06:28:42 UTC 2020
+who rin
+file src/sys/arch/sun2/conf/Makefile.sun2: 1.25
+descr Work around for reproducible kernel freezes just after ``Starting
+ postfix.'', where I cannot even enter DDB nor obtain crash dump.
+ I still haven't figured out why. Possibly something wrong with -Os
+ optimization level for GCC/m68k, cf.,
+ http://mail-index.netbsd.org/port-sun3/2020/07/19/msg000166.html
+kcah