Re: ILP32 toolchain status update

2017-11-08 Thread Maxim Kuvyrkov
> 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 that decision? Hi Andrew, Where such a decision was discussed? -- Maxim Kuvyrkov www.linaro.org > > Thanks, > Andrew > > -

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: [hpc-sig-devel] Re: [FYI] HCQC(HPC compiler quality checker) on GitHub

2017-11-08 Thread Yvan Roux
On 8 November 2017 at 18:58, Masaki Arai wrote: > Hi, > > Thank you very much for your reply. > > I committed the PDF file on GitHub. > Please download it from >URL: https://github.com/Linaro/hcqc/blob/master/doc/hcqc-2017-11-07.pdf Thanks a lot Masaki. > Best regards, > > -- >

Re: [hpc-sig-devel] Re: [FYI] HCQC(HPC compiler quality checker) on GitHub

2017-11-08 Thread Masaki Arai
Hi, Thank you very much for your reply. I committed the PDF file on GitHub. Please download it from URL: https://github.com/Linaro/hcqc/blob/master/doc/hcqc-2017-11-07.pdf Best regards, -- -- Masaki Arai ___ lin

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: [hpc-sig-devel] Re: [FYI] HCQC(HPC compiler quality checker) on GitHub

2017-11-08 Thread Yvan Roux
On 8 November 2017 at 18:31, Renato Golin wrote: > On 8 November 2017 at 17:30, Luis Machado wrote: >> FTR, i don't see any attached PDF's in this e-mail either. > > It's possible that the pdf went to hpc-sig-dev and not toolchain. > maybe toolchain doesn't allow attachments? something like that

Re: [hpc-sig-devel] Re: [FYI] HCQC(HPC compiler quality checker) on GitHub

2017-11-08 Thread Yvan Roux
On 8 November 2017 at 18:25, Renato Golin wrote: > On 8 November 2017 at 17:19, Masaki Arai wrote: >> Hi, >> >> I am sorry for the inconvenience. >> >> #I'm not sure what is going on. >> #I can extract PDF from my first e-mail.!? > > > I could see the PDF on the first email, and on this one too.

Re: [hpc-sig-devel] Re: [FYI] HCQC(HPC compiler quality checker) on GitHub

2017-11-08 Thread Renato Golin
On 8 November 2017 at 17:30, Luis Machado wrote: > FTR, i don't see any attached PDF's in this e-mail either. It's possible that the pdf went to hpc-sig-dev and not toolchain. maybe toolchain doesn't allow attachments? ___ linaro-toolchain mailing list

Re: [FYI] HCQC(HPC compiler quality checker) on GitHub

2017-11-08 Thread Luis Machado
FTR, i don't see any attached PDF's in this e-mail either. On 11/08/2017 12:18 PM, Yvan Roux wrote: Hi Masaki, On 8 November 2017 at 04:38, Masaki Arai wrote: Hi, I put HCQC(HPC compiler quality checker) on GitHub. URL: https://github.com/Linaro/hcqc Any comments or suggestions are very

Re: [hpc-sig-devel] Re: [FYI] HCQC(HPC compiler quality checker) on GitHub

2017-11-08 Thread Renato Golin
On 8 November 2017 at 17:19, Masaki Arai wrote: > Hi, > > I am sorry for the inconvenience. > > #I'm not sure what is going on. > #I can extract PDF from my first e-mail.!? I could see the PDF on the first email, and on this one too. :) --renato ___ l

Re: [FYI] HCQC(HPC compiler quality checker) on GitHub

2017-11-08 Thread Yvan Roux
Hi Masaki, On 8 November 2017 at 04:38, Masaki Arai wrote: > Hi, > > I put HCQC(HPC compiler quality checker) on GitHub. > > URL: https://github.com/Linaro/hcqc > > Any comments or suggestions are very welcome. > I am going to improve README.md overall and to add more test programs. > I will al

[ANNOUNCE] Linaro Binary Toolchain Release-Candidate GCC 7.2-2017.11-rc1

2017-11-08 Thread Przemyslaw Wirkus
The Linaro Binary Toolchain The Linaro GCC 7.2-2017.11-rc1 Release-Candidate is now available. *Notice*: GCC 7.1 ABI change for arm*-*-* targets, and note for aarch64*-*-* targets From GCC 7.1 release notes: On ARM targets (arm*-*-*), a bug introduced in GCC 5 that

[ANNOUNCE] Linaro Binary Toolchain Release-Candidate GCC 6.4-2017.11-rc1

2017-11-08 Thread Przemyslaw Wirkus
The Linaro Binary Toolchain The Linaro GCC 6.4-2017.11-rc1 Release-Candidate is now available. The GCC 6 Release series has significant changes from the GCC 5 release series. For an explanation of the changes please see the following website: https://gcc.gnu

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

[FYI] HCQC(HPC compiler quality checker) on GitHub

2017-11-08 Thread Masaki Arai
Hi, I put HCQC(HPC compiler quality checker) on GitHub. URL: https://github.com/Linaro/hcqc Any comments or suggestions are very welcome. I am going to improve README.md overall and to add more test programs. I will also report the analysis results using HCQC on hpc-sig-devel. The attached PD

RE: ILP32 toolchain status update

2017-11-08 Thread Pinski, Andrew
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 >2. [GLIBC] LP64 glibc libthread_db does not support ILP32. No change to glibc was needed to fix this, only the above changes to gdb were needed