It would be best to file a bug in glibc then and fix it there.
From: Kugan kugan.vivekanandara...@linaro.org
Sent: Sunday, May 10, 2015 10:46 PM
To: Pinski, Andrew; Linaro Toolchain
Subject: Re: [ACTIVITY] 04 May -- 08 May
On 11/05/15 15:24, Pinski
] 04 May -- 08 May
== Progress ==
* Upstream GCC (4/10)
- TCWG-779 Vector rtx costs for AArch64 ACKed to commit.
- Asked to do fresh regression and benchmarking
- re-based to latest trunk
- Trunk is broken and narrowed down the failure to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66066
== Progress ==
* Upstream GCC (4/10)
- TCWG-779 Vector rtx costs for AArch64 ACKed to commit.
- Asked to do fresh regression and benchmarking
- re-based to latest trunk
- Trunk is broken and narrowed down the failure to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66066
- Fixed and regression
Sent: Sunday, May 10, 2015 10:46 PM
To: Pinski, Andrew; Linaro Toolchain
Subject: Re: [ACTIVITY] 04 May -- 08 May
On 11/05/15 15:24, Pinski, Andrew wrote:
- Trunk is broken and narrowed down the failure to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66066
No the code is broken in SPEC
On 11/05/15 15:24, Pinski, Andrew wrote:
- Trunk is broken and narrowed down the failure to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66066
No the code is broken in SPEC ;). SPEC INT has been known to be broken C and
they are not willing to do anything about it after the fact. This
