On Sat, Jul 30, 2016 at 12:07 AM, Jim Wilson wrote:
> On Fri, Jul 29, 2016 at 7:55 PM, Jeffrey Walton wrote:
>>> Yes, these *p128* intrinsics are missing from the aarch64 port. I'd
>>> suggest filing a bug report.
>>
>> Please forgive my ignorance. Who
On Fri, Jul 29, 2016 at 7:55 PM, Jeffrey Walton wrote:
>> Yes, these *p128* intrinsics are missing from the aarch64 port. I'd
>> suggest filing a bug report.
>
> Please forgive my ignorance. Who gets the report? Linaro, Debian or GCC?
The FSF GCC bugzilla.
On Fri, Jul 29, 2016 at 7:04 PM, Jeffrey Walton wrote:
> How does one build an Aarch32 program on Aarch64?
The arm and aarch64 compilers are separate compiler ports. So you
need two different compilers, an arm compiler and an aarch64 compiler.
The arm compiler emits only
On Thu, Jul 28, 2016 at 12:28 PM, Jim Wilson wrote:
> On Thu, Jul 28, 2016 at 8:36 AM, Jeffrey Walton wrote:
>> I'm having trouble finding vreinterpretq_u64_p128 (and friends) to
>> help convert a polynomial. I can't find it in arm_neon.h or
>>
Hi Everyone,
I have a HiKey running Linaro. I'm trying to build out a test case
which tests Aarch32 on Aarch64.
When I attempt to build an Aarch32 binary I experience the compile
error below. The GCC folks helped me with the Aarch32 CFLAGS, so I
believe they are correct.
$ gcc
== Progress ==
* PR24234 - [AArch64] error in backend: fixup value out of range
[TCWG-681] [5/10]
- Wrong instruction size computed for TLS accesses
- Accepted upstream, will commit first thing next week
* [AArch64] Register all AArch64 passes [TCWG-687] [3/10]
- Cleanup that should enable
* Off on Tue and Wed [4/10]
# Progress #
* TCWG-655, workaround ARM linux kernel ptrace bug on setting VFP
registers. Pedro isn't happy about the workaround, and inclined to
upgrade kernel.
* TCWG-685, GDB 7.12 release. [4/10]
Fix a bug on threads are disappeared when gdb detach. GDB
The Linaro Binary Toolchain
The Linaro GCC 5.3-2016.05 Release is now available.
Notice: All Linaro GCC 5 series toolchain users should migrate to the
latest version of the Linaro GCC 5 toolchain in order to mitigate
potential security exposure to CVE-2015-7547. See