Is CPUTYPE=cortex-A7 supposed to work?

Michal Meloun melounmichal at gmail.com
Thu Mar 16 16:51:52 UTC 2017



On 16.03.2017 17:14, Sylvain Garrigues wrote:
>
>> Le 16 mars 2017 à 16:16, Michal Meloun <melounmichal at gmail.com
>> <mailto:melounmichal at gmail.com>> a écrit :
>>
>> Firstly, thanks to Andrew for perfect bug analysis.
>> Currently, you can compile you kernel/userland/port with CPUTYPE/CFLAGS
>> without any additional problem(s). I use this for all my ARM systems for
>> more that last 6-months...
>>
>> The 'other' interfaces are gdb, porcfs, libpthtread. I work on this, but
>> I still have not any output.
>
> Thank you so much for your quick feedback Michal. Good to know this
> matter is into good hands. I’m afraid I'm still afraid about `basic’
> programs like git being still potentially broken when
> kernel+world+ports have CPUTYPE=cortex-a7 in make.conf - Andrew said a
> simple `git clone' could fail, more precisely (quoting him):
>> I have determined that the sha1 failures occur only if the NEON-enabled
>> SHA1 block function is interrupted by a signal. This explains why it
>> fails in git (which is using SIGALRM to set a "display progress" flag)
>> but not in standalone SHA1 tests;
>
> Removing CPUTYPE apparently fixes things hence I’m not 100% confident
> yet of keeping CPUTYPE=cortex-a7 myself even if only a few ports might
> be affected. Git is an important port, who knows what other ports are
> broken :-) Are you also working on the kernel part (as part of the
> ‘other interfaces’ you mentioned) to fix this
> fp-register-preserving-during-signal? 
>
No, the issue is very clear (again, thanks to Andrew), and it's not
related to CPUTYPE.

Is this enough to confirm that the FPU instructions in a signal handler
is not used so frequently?
https://imagebin.ca/v/3FmLkPuRZ1IO
All used ports from this picture (KDE4, LibreOffice + dependencies ) are
built on Jetson TK1, with -mcpu=Cortex-A15
 
Michal



More information about the freebsd-arm mailing list