On Nov 9, 2017, at 9:44 AM, Pinski, Andrew Andrew.Pinski@cavium.com wrote:
Where such a decision was discussed?
This was discussed back in the end of June. Mark Hambleton of ARM sent a response to Cavium to that effect.
Hi Andrew,
There must have been a miscommunication then. ARM did not ask Linaro to take over development of ILP32. ARM has asked Linaro to produce a binary cross-toolchain from components published on upstream ILP32 branches.
Linaro has no current plans to work on ILP32 support in binutils/gdb/glibc. We do plan to finish ILP32 sanitizer support in GCC -- because Adhemerval has the most experience with AArch64/AArch32 sanitizers in ARM ecosystem.
Returning to GDB failures, it seems that patches you referenced (posted in March 2017) do not address the debugger deficiencies listed in at the start of this thread. Yao will follow up on that.
-- Maxim Kuvyrkov www.linaro.org
-----Original Message----- From: Maxim Kuvyrkov [mailto:maxim.kuvyrkov@linaro.org] Sent: Wednesday, November 8, 2017 10:32 PM To: Pinski, Andrew Andrew.Pinski@cavium.com Cc: Yao Qi yao.qi@linaro.org; Linaro Toolchain linaro-toolchain@lists.linaro.org; Szabolcs Nagy szabolcs.nagy@arm.com; Ellcey, Steve Steve.Ellcey@cavium.com Subject: Re: ILP32 toolchain status update
On Nov 8, 2017, at 9:03 PM, Pinski, Andrew Andrew.Pinski@cavium.com wrote:
I thought the decision Linaro/Arm was going to take over the development of the ILP32? What happened to that decision?
Hi Andrew,
Where such a decision was discussed?
-- Maxim Kuvyrkov www.linaro.org
Thanks, Andrew
-----Original Message----- From: Yao Qi [mailto:yao.qi@linaro.org] Sent: Wednesday, November 8, 2017 9:50 AM To: Pinski, Andrew Andrew.Pinski@cavium.com Cc: Maxim Kuvyrkov maxim.kuvyrkov@linaro.org; Linaro Toolchain linaro-toolchain@lists.linaro.org; Szabolcs Nagy szabolcs.nagy@arm.com; Ellcey, Steve Steve.Ellcey@cavium.com Subject: Re: ILP32 toolchain status update
On 8 November 2017 at 16:56, Pinski, Andrew Andrew.Pinski@cavium.com wrote:
What env are you using? Are the glibc versions on the same between ILP32 and LP64? Because when that was true I did not have any issues with libthread_db.
I didn't run gdb tests in ILP32 env, and I don't have such env. I got gdb.sum from Steve on 18 Oct. You are on the cc as well. All my analysis is based on that gdb.sum.
Anyways I did not see some of those failures listed below when using the correct setup.
OK, can you send me a gdb.sum?
-- Yao Qi