Re: ILP32 toolchain status update

2017-11-14 Thread Maxim Kuvyrkov
t. -- Maxim Kuvyrkov www.linaro.org > > -Original Message- > From: Maxim Kuvyrkov [mailto:maxim.kuvyr...@linaro.org] > Sent: Wednesday, November 8, 2017 10:32 PM > To: Pinski, Andrew > Cc: Yao Qi ; Linaro Toolchain > ; Szabolcs Nagy ; > Ellcey, Steve > Subject:

Re: ILP32 toolchain status update

2017-11-14 Thread Yao Qi
On 7 November 2017 at 13:35, Pinski, Andrew wrote: > Note gdb patches are located at: > https://sourceware.org/ml/binutils/2017-03/msg00075.html > https://sourceware.org/ml/gdb-patches/2017-03/msg00051.html > Hi Andrew, These two patches are the patches Steve sent to us some days ago, and we've a

RE: ILP32 toolchain status update

2017-11-09 Thread Pinski, Andrew
rew Cc: Yao Qi ; Linaro Toolchain ; Szabolcs Nagy ; Ellcey, Steve Subject: Re: ILP32 toolchain status update > On Nov 8, 2017, at 9:03 PM, Pinski, Andrew wrote: > > I thought the decision Linaro/Arm was going to take over the development of > the ILP32? > What happened to

RE: ILP32 toolchain status update

2017-11-09 Thread Pinski, Andrew
Toolchain ; Szabolcs Nagy ; Ellcey, Steve Subject: Re: ILP32 toolchain status update On 8 November 2017 at 16:56, Pinski, Andrew 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 libthr

RE: ILP32 toolchain status update

2017-11-09 Thread Pinski, Andrew
[mailto:yao...@linaro.org] Sent: Wednesday, November 8, 2017 1:16 AM To: Pinski, Andrew Cc: Maxim Kuvyrkov ; Linaro Toolchain ; Szabolcs Nagy ; Ellcey, Steve Subject: Re: ILP32 toolchain status update On 7 November 2017 at 13:35, Pinski, Andrew wrote: > Note gdb patches are located at: >

Re: ILP32 toolchain status update

2017-11-08 Thread Maxim Kuvyrkov
> Thanks, > Andrew > > -Original Message- > From: Yao Qi [mailto:yao...@linaro.org] > Sent: Wednesday, November 8, 2017 9:50 AM > To: Pinski, Andrew > Cc: Maxim Kuvyrkov ; Linaro Toolchain > ; Szabolcs Nagy ; > Ellcey, Steve > Subject: Re: ILP32 toolchain sta

Re: ILP32 toolchain status update

2017-11-08 Thread Adhemerval Zanella
On 08/11/2017 15:49, Yao Qi wrote: > On 8 November 2017 at 16:56, Pinski, Andrew 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

Re: ILP32 toolchain status update

2017-11-08 Thread Yao Qi
On 8 November 2017 at 16:56, Pinski, Andrew 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 fro

Re: ILP32 toolchain status update

2017-11-08 Thread Yao Qi
On 7 November 2017 at 13:35, Pinski, Andrew wrote: > Note gdb patches are located at: > https://sourceware.org/ml/binutils/2017-03/msg00075.html > https://sourceware.org/ml/gdb-patches/2017-03/msg00051.html > > All these TODOs are given based on the observations of gdb tests result with these two

RE: ILP32 toolchain status update

2017-11-08 Thread Pinski, Andrew
org] On Behalf Of Maxim Kuvyrkov Sent: Tuesday, November 7, 2017 4:40 AM To: Linaro Toolchain Cc: Szabolcs Nagy ; Ellcey, Steve Subject: ILP32 toolchain status update Over the last couple of months arm64 community and us have tested various aspects of ILP32 toolchain and, while most of

ILP32 toolchain status update

2017-11-07 Thread Maxim Kuvyrkov
Over the last couple of months arm64 community and us have tested various aspects of ILP32 toolchain and, while most of toolchain works as expected, several features are still missing. Most of the work left is on GDB side, especially using LP64 GDB to debug ILP32 applications. 1. [GCC] GCC san