CURRENT: EFI boot failure

[Harald Schmalzbauer]

 Bezüglich O. Hartmann's Nachricht vom 04.10.2014 08:47 (localtime):

…
>> 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
>>
> Has this problem anyhow seriously been addressed? I run into this very often on several
> platforms with HAswell-based CPUs (other systems with IvyBridge or SandyBridge are still
> to be migrated to UEFI boot, so I do not have any older architectures at hand to proof
> whether this issue is still present or not on Non-AVX2 systems.
>
> If there is no progress so far, would it be well-advised to open a PR?

Unofrtunately I don't really have qualified knwoledge about compiler
optimazations nor any efi binary knwoledge.
Opening a PR is really needed, this issue shouldn't be left unchecked.
But I'd prefer if someone does it, who understands what Matt Fleming
answered in
http://lists.freebsd.org/pipermail/freebsd-current/2014-September/052354.html

Anyone?

Thanks,

-Harry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-current/attachments/20141016/7cbfc287/attachment.sig>