Re: Proposal for the transition timetable for the move to GIT

2020-01-08 Thread Jeff Law
On Wed, 2020-01-08 at 23:34 +, Joseph Myers wrote: > > As noted on overseers, once Saturday's DATESTAMP update has run at 00:16 > UTC on Saturday, I intend to add a README.MOVED_TO_GIT file on SVN trunk > and change the SVN hooks to make SVN readonly, then disable gccadmin's > cron jobs tha

Re: Proposal for the transition timetable for the move to GIT

2020-01-08 Thread Segher Boessenkool
On Wed, Jan 08, 2020 at 11:34:32PM +, Joseph Myers wrote: > As noted on overseers, once Saturday's DATESTAMP update has run at 00:16 > UTC on Saturday, I intend to add a README.MOVED_TO_GIT file on SVN trunk > and change the SVN hooks to make SVN readonly, then disable gccadmin's > cron jobs

Comparing types at LTO time

2020-01-08 Thread Gary Oblock
There doesn't seem to be a way to compare types at LTO time. The functions same_type_p and comptypes are front end only if I'm not totally confused (which is quite possible) and type_hash_eq doesn't seem to apply for structure types. Please, any advice would be welcome. Thanks, Gary Oblock

Re: Proposal for the transition timetable for the move to GIT

2020-01-08 Thread Joseph Myers
On Wed, 8 Jan 2020, Eric S. Raymond wrote: > They use your feedback to find places where their comment-processing > scripts could be improved; we've used it learn what additional > oddities in ChangeLogs we need to be able to handle automatically. I've used comparisons of authors in the two conve

Re: Proposal for the transition timetable for the move to GIT

2020-01-08 Thread Eric S. Raymond
Maxim Kuvyrkov : > Once gcc-reparent conversion is regenerated, I'll do another round of > comparisons between it and whatever the latest reposurgeon version is. Thanks, Maxim. Those comparisons have been very helpful to Joseph and Richard and to the reposurgeon devteam as well. They use your fe

Re: Proposal for the transition timetable for the move to GIT

2020-01-08 Thread Maxim Kuvyrkov
> On Dec 30, 2019, at 7:08 PM, Richard Earnshaw (lists) > wrote: > > On 30/12/2019 15:49, Maxim Kuvyrkov wrote: >>> On Dec 30, 2019, at 6:31 PM, Richard Earnshaw (lists) >>> wrote: >>> >>> On 30/12/2019 13:00, Maxim Kuvyrkov wrote: > On Dec 30, 2019, at 1:24 AM, Richard Earnshaw (lists)

[INTERNAL] LLVM v9.0.1

2020-01-08 Thread Rogerio de Souza Moraes
Hi everyone, LLVM v9.0.1 is available at folder “/grid/common/test/llvm-v9.0.1rh65”, for lnx86 platform. This release contains bug-fixes for the LLVM 9.0.0 release. This release is API and ABI compatible with 9.0.0. It is NOT officially supported by Cadence and should NOT be used to compile Ca

Re: Frontend access to target-related options

2020-01-08 Thread The Other
I'm just working from the somewhat incomplete Rust spec at this point - intrinsics and other complicated target-dependent stuff don't seem to be part of it. Rust seems to provide vector intrinsics through libraries with inline assembly. For the frontend, I just need a list of strings describing th

Re: Frontend access to target-related options

2020-01-08 Thread Andrew Pinski
On Wed, Jan 8, 2020 at 1:16 AM The Other wrote: > > I've found the code for the target hooks for both the C-family and D > frontends (or at least their implementation for the i386 platform). The > C-family ones seem like they probably are too tied to the preprocessor to > be usable for other langu

__patchable_function_entries is flawed

2020-01-08 Thread Fangrui Song
On 2020-01-07, Szabolcs Nagy wrote: On 07/01/2020 07:25, Fangrui Song wrote: On 2020-01-06, Fangrui Song wrote: The addresses of NOPs are collected in a section named __patchable_function_entries. A __patchable_function_entries entry is relocated by a symbolic relocation (e.g. R_X86_64_64, R_

Re: Frontend access to target-related options

2020-01-08 Thread The Other
I've found the code for the target hooks for both the C-family and D frontends (or at least their implementation for the i386 platform). The C-family ones seem like they probably are too tied to the preprocessor to be usable for other languages (which I assume is the reason that the D frontend crea

Weekly Notice-AICSE2020 Invite Papers for Pub.(Ei|CPCI|SCOPUS)

2020-01-08 Thread Dani
| | | | 01 CALL FOR PAPERS | | Now Submit Research Paper to AICSE2020 Dear authors and scholars, we, as the committee members and speakers, heartily welcome you to Shang-hai (China) for attendance at the AICSE2020 -2020 International Conference on Artificial Intelligence, Computer and Software E