title: Linaro version vs GCC version
body: <p>I have just noticed that Linaro version and GCC version do not match.</p>
  
  <p>As of today current stable version of GCC is <a href="https://gcc.gnu.org/" rel="nofollow noreferrer">6.2</a>.</p>
  
  <p>Current stable version of Linaro is <a href="https://releases.linaro.org/components/toolchain/binaries/latest/arm-eabi/" rel="nofollow noreferrer">6.1-2016.08</a> (link from Linaro's main page).</p>
  
  <p>There is also Linaro version <a href="https://releases.linaro.org/components/toolchain/binaries/" rel="nofollow noreferrer">6.2-2016.11</a> available for download.</p>
  
  <p>Release notes for <a href="http://releases.linaro.org/components/toolchain/binaries/6.1-2016.08/" rel="nofollow noreferrer">Linaro 6.1-2016.08</a> and <a href="http://releases.linaro.org/components/toolchain/binaries/6.2-2016.11/" rel="nofollow noreferrer">Linaro 6.2-2016.11</a> contain information about GCC 6 with the <a href="https://gcc.gnu.org/gcc-6/changes.html" rel="nofollow noreferrer">link</a> to its release notes.</p>
  
  <p>Based on it I expected that Linaro 6.1-2016.08 and Linaro 6.2-2016.11 are based on GCC 6.1 and GCC 6.2 respectively.</p>
  
  <p>But it turned out that actual version of GCC in Linaro builds is 5.3:</p>
  
  <pre><code>yurko@my_pc /cygdrive/f/Linaro/gcc-linaro-6.1.1-2016.08-i686-mingw32_arm-eabi/bin
  $ arm-eabi-gcc.exe -E -dM - &lt; /dev/null | grep __GNUC__
  #define __GNUC__ 5
  
  yurko@my_pc /cygdrive/f/Linaro/gcc-linaro-6.1.1-2016.08-i686-mingw32_arm-eabi/bin
  $ arm-eabi-gcc.exe --version
  arm-eabi-gcc.exe (GCC) 5.3.0
  
  
  yurko@my_pc /cygdrive/f/Linaro/gcc-linaro-6.2.1-2016.11-i686-mingw32_arm-eabi/bin
  $ arm-eabi-gcc.exe -E -dM - &lt; /dev/null | grep __GNUC__
  #define __GNUC__ 5
  
  yurko@my_pc /cygdrive/f/Linaro/gcc-linaro-6.2.1-2016.11-i686-mingw32_arm-eabi/bin
  $ arm-eabi-gcc.exe --version
  arm-eabi-gcc.exe (GCC) 5.3.0
  </code></pre>
  
  <p><a href="https://wiki.linaro.org/WorkingGroups/ToolChain/FAQ" rel="nofollow noreferrer">Linaro GCC FAQ Page</a> says nothing about it.</p>