Displaying 3 results from an estimated 3 matches for "r223477".
Did you mean:
r223478
2015 Jan 30
0
[LLVMdev] ARM regression between r223766 and r223925
...o-integrated-as. BUT my build script log shows that I successfully
> cross-compiled with NEON on December 4 2014. I usually do basic
> testing of those builds on ARMv7. So, I suggest trying to bootstrap
> r223339 with NEON. Thats the last commit for Dec 3.
Right, I've already checked r223477 (5th Dec) to be green, so that
should do for the good end.
Since you reported on the 13th Dec that "trunk" was broken, I'm
assuming you checked out and built, which would put the bad side
earlier than the 14th Dec.
It's 9 days to look at, but at least it's better than 6 mont...
2015 Jan 30
2
[LLVMdev] ARM regression between r223766 and r223925
On Fri, Jan 30, 2015 at 7:20 PM, Renato Golin <renato.golin at linaro.org> wrote:
> On 30 January 2015 at 17:18, İsmail Dönmez <ismail at donmez.ws> wrote:
>> My analysis was completely wrong because I had -no-integrated-as
>> sneaked in libcxxabi CMakeLists.txt and then somehow I reverted it
>> which showed me the initial failure. The Neon failure is completely
2015 Jan 30
2
[LLVMdev] ARM regression between r223766 and r223925
...my build script log shows that I successfully
>> cross-compiled with NEON on December 4 2014. I usually do basic
>> testing of those builds on ARMv7. So, I suggest trying to bootstrap
>> r223339 with NEON. Thats the last commit for Dec 3.
>
> Right, I've already checked r223477 (5th Dec) to be green, so that
> should do for the good end.
Nice!
> Since you reported on the 13th Dec that "trunk" was broken, I'm
> assuming you checked out and built, which would put the bad side
> earlier than the 14th Dec.
Indeed.
> It's 9 days to look at,...