Bezüglich Harald Schmalzbauer's Nachricht vom 23.09.2014 16:28 (localtime): > Bezüglich O. Hartmann's Nachricht vom 19.09.2014 15:22 (localtime): >> … >> The problem I reported about in the first place is triggered by a faulty >> loader.efi that >> arises, when optimisation level is -O3. -O2 works fine. > I can confirm that this problem also shows up when using > 'CPUTYPE?=core-avx2' > Setting CPUTYPE to core-avx-i doesnt ehibit the problem. > > I could narrow down the cause to libefi.a (sys/boot/efi). > But I don't understand the things going on there, so no clue how to fix > besides maybe > > --- sys/boot/efi/Makefile.inc.orig 2014-09-23 16:22:46.000000000 +0200 > +++ sys/boot/efi/Makefile.inc 2014-09-23 16:25:16.000000000 +0200 > @@ -2,6 +2,10 @@ > > BINDIR?= /boot > > +.ifdef CPUTYPE > +.undef CPUTYPE > +.endif
Sorry, forget the suggestion, it doesn't work since it leads to CFLAG -march="" and the same problem occurs. For my case this works: --- sys/boot/efi/Makefile.inc.orig 2014-09-23 16:22:46.000000000 +0200 +++ sys/boot/efi/Makefile.inc 2014-09-23 16:46:30.000000000 +0200 @@ -2,6 +2,10 @@ BINDIR?= /boot +.if ${CPUTYPE} == "core-avx2" +CPUTYPE= core-avx-i +.endif + .if ${MACHINE_CPUARCH} == "i386" CFLAGS+= -march=i386 .endif JFI -Harry
signature.asc
Description: OpenPGP digital signature