[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/17212] Tag_CPU_name merging produces wrong tag.

From: nickc at redhat dot com
Subject: [Bug ld/17212] Tag_CPU_name merging produces wrong tag.
Date: Tue, 09 Sep 2014 16:00:56 +0000


Nick Clifton <nickc at redhat dot com> changed:

           What    |Removed                     |Added
             Status|NEW                         |ASSIGNED

--- Comment #3 from Nick Clifton <nickc at redhat dot com> ---
Hi Maxim,

  [Sorry for the delay in responding to this problem].

  The simplest answer to your question is: "yes, this is the expected
behaviour".  If you use a cortex-a8 targeted toolchain you will get a binary
tagged with a cortex-a8 Tag_CPU_name.  If you want a cortex-a15 tagged binary
then use a cross toolchain specifically configured to target the cortex-a15.

  As Yuri pointed out, maybe we should be examining other tags when merging two
architecture tags.  But I suspect that this will open a can of worms that will
prove to be too difficult to manage.  Keep it simple is my advice.  Use an a8
toolchain for creating a8 binaries and an a15 toolchain for creating a15


You are receiving this mail because:
You are on the CC list for the bug.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]