Bug#791985: Please support ARM64 (ucontext_t)

guy develop at faert.net
Sat Jul 11 19:36:59 UTC 2015


Hello Mika and Martin,

I used to have some i386 and amd64 specific assembler code for hash 
calculation in Guymager (not libguytools) in the past, but it always was 
backed up by C-code for other architectures. The reason for limiting 
Guymager to i386, amd64 and powerpc is that I have no real HW for 
testing with other architectures.

For libguytools it's a bit different. Those few lines mentioned by 
Martin are in fact architecture dependent - and I know of no way to do 
it differently (please correct me if I'm wrong). Fortunately, arm and 
arm64 should be easy to add. It set up an arm64 VM in qemu yesterday and 
I'll test it next week. I'll let you know about the result and the 
necessary changes in toolsignal.cpp.

Greetings

Guy



On 10.07.2015 12:12, Michael Prokop wrote:
> Hi Martin :)
>
> Cc-ing Guy, upstream of libguytools + guymager
>
> * Martin Michlmayr [Thu Jul 09, 2015 at 03:32:01PM -0400]:
>> Package: libguytools2
>> Version: 2.0.3-1
>> Severity: wishlist
>> User:debian-arm at lists.debian.org
>> Usertags: arm64 port
>> This package fails to build on arm64, but a quick looks suggests
>> this package might be useful on arm64.  Do you know if upstream or
>> someone else is working on arm64 support ("aarch64") already?
>> The only arch specific code I could fine was in toolsignal.cpp:
>>        #if   defined(__i386__)
>>           pIP = (void*) pUContext->uc_mcontext.gregs[REG_EIP];
>>        #elif defined(__x86_64__)
>>           pIP = (void*) pUContext->uc_mcontext.gregs[REG_RIP];
>>        #elif defined(__hppa__)
>>           pIP = (void*) pUContext->uc_mcontext.sc_iaoq[0] & ~0x3UL;
>>        #elif (defined (__ppc__)) || (defined (__powerpc__))
>>           pIP = (void*) pUContext->uc_mcontext.regs->nip;
>>        #endif
> The only consumer of libguytools is guymager, which itself is
> "Architecture: amd64 i386 powerpc" only (due to some architecture
> specific optimizations for performance reasons AFAIK), so I'm not
> sure what Guy as upstream thinks of that. Opinions? :)
>
> regards,
> -mika-



More information about the forensics-devel mailing list