Entirely relevant. RISC vs. CISC. https://www.electronicshub.org/risc-and ... itectures/Is it relevant that the Pi uses an ARM processor instead of conventional one you'd find in a desktop?
The code is C/C++, the only part I can see that directly uses inline asm has checks to use a default backup for non-x86 architectures (reading the time-stamp counter and hardware random numbers). Unless there is use of x86 intrinsics without backups for non-x86 then there shouldn't be much (if any) modifications needed.The Traveler wrote: ↑Wed Jun 13, 2018 2:13 amIt would be more difficult (read: a lot of work) to port from x32/x64 to ARM in my opinion because of the reduced instruction set in RISC. This would be reflected in the compiler and necessitate some creative coding to work around (if possible at all) missing functions.
Check the configure or make file. Look for the section labeled "install". It should provide clues to where it installs the files. Depending on any user supplied install path prefixes, usually executable files end up in /usr/bin or /usr/local/bin and the library files in /usr/lib or usr/local/lib. It's not a hard and fast rule but it applies generally.The problem is I don't know where to find the finished, compiled files. Any idea where they would go?
Users browsing this forum: No registered users and 33 guests