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

2019-12-31 Thread Segher Boessenkool
On Mon, Dec 30, 2019 at 06:23:16PM -0600, Segher Boessenkool wrote: > > To me, that indicates that using a conversion tool that is conservative in > > its heuristics, and then selectively applying improvements to the extent > > they can be done safely with manual review in a reasonable time, is b

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

2019-12-31 Thread Joseph Myers
On Mon, 16 Dec 2019, Jeff Law wrote: > > Joseph Myers has made his choice. He has said repeatedly that he > > wants to follow through with the reposurgeon conversion, and he's > > putting his effort behind that by writing tests and even contributing > > code to reposurgeon. > > > > We'll get thi

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

2019-12-31 Thread Richard Earnshaw (lists)
On 31/12/2019 13:42, Joseph Myers wrote: > On Mon, 16 Dec 2019, Jeff Law wrote: > >>> Joseph Myers has made his choice. He has said repeatedly that he >>> wants to follow through with the reposurgeon conversion, and he's >>> putting his effort behind that by writing tests and even contributing >>

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

2019-12-31 Thread Segher Boessenkool
On Tue, Dec 31, 2019 at 01:42:55PM +, Joseph Myers wrote: > As the remaining changes being made to the reposurgeon conversion are of > the form "tidy things up where reposurgeon is already making a reasonable > conservative choice but minor improvements are still possible", I think > it's ve

Re: Does gcc automatically lower optimization level for very large routines?

2019-12-31 Thread Andi Kleen
Qing Zhao writes: > (gdb) where > #0 0x00ddbcb3 in df_chain_create (src=0x631006480f08, > dst=0x63100f306288) at ../../gcc-8.2.1-20180905/gcc/df-problems.c:2267 > #1 0x001a in df_chain_create_bb_process_use ( > local_rd=0x7ffc109bfaf0, use=0x63100f306288, top_fla