title: Differences between arm64 and aarch64
body: <p>I have two "unlocked" devices, an iPad mini 3, and a Galaxy Edge 6, both endowed with a terminal and a minimalistic set of unix commands. I thought both devices have arm64 processors but when I ran</p>
  
  <pre><code>uname -a
  </code></pre>
  
  <p>on both devices I got the following :</p>
  
  <p>for the iPad mini 3 :</p>
  
  <pre><code>xxxxs-iPad:/var/mobile root# uname -a
  Darwin xxxx-iPad 14.0.0 Darwin Kernel Version 14.0.0: Wed Jun 24 00:50:15 PDT 2015; root:xnu-2784.30.7-30/RELEASE_ARM64_S5L8960X iPad4, **arm64**, J85mAP
  </code></pre>
  
  <p>for the Samsung Galaxy s6 Edge :</p>
  
  <pre><code>u0_a203@zerolte:/ $ uname -a
  Linux localhost 3.10.61-4497415 #1 SMP PREEMPT Thu Apr 9 15:06:40 KST 2015 **aarch64** GNU/Linux
  </code></pre>
  
  <p>If I am not wrong, the last info in both case, J85mAP and GNU/Linux, stand for firmwares, and the antepenultimate infos, arm64 and aarch64, stand for the processors.</p>
  
  <p>My questions are the following : obviously the strings "arm64" and "aarch64" are not the same, but I always thought arm64 and aarch64 were the same. (It's even told when you put the arm64 tag to a question here.)  </p>
  
  <p>So, are they really identical?  </p>
  
  <p>Especially, what should I worry about in case of cross-building libraries for both targets ? In fact, I have gcc 5.2.0 in mind, but maybe also lower versions. Can I just pass</p>
  
  <pre><code>-target=arm64
  </code></pre>
  
  <p>or</p>
  
  <pre><code>-target=aarch64
  </code></pre>
  
  <p>according to which device I target and just worry about the rest of options to configure?</p>
  
  <p><strong>EDIT</strong> Hum, look for this again, without success.</p>