Re: Good news, bad news on the repository conversion

2018-07-10 Thread Eric S. Raymond
Mark Atwood : > ESR, how much for the memory expansion? It sounds like we have some > volunteers to solve this problem with some money. That's now rthe second problem out. There's a malformation that has turned up in the repo that may sink the conversion entirely. I want to be reasonably sure I

Re: Good news, bad news on the repository conversion

2018-07-10 Thread Mark Atwood
ESR, how much for the memory expansion? It sounds like we have some volunteers to solve this problem with some money. ..m On Tue, Jul 10, 2018 at 2:14 AM Aldy Hernandez wrote: > Wait, there's a pot of money for making SVN go away? Sign me up! > While we're at it, let's start one for TCL and d

Re: -Wclass-memaccess warning should be in -Wextra, not -Wall

2018-07-10 Thread Soul Studios
I guess the phrasing is a bit weak, "some users" obviously has to refer to a significant proportion of users, "easy to avoid" cannot have too many drawbacks (in particular, generated code should be of equivalent quality), etc. -Wclass-memaccess fits the "easy to avoid" quite well, since a simp

Re: -Wclass-memaccess warning should be in -Wextra, not -Wall

2018-07-10 Thread Soul Studios
Not sure how kosher it is to address several replies in one email, but I'm going to attempt it as there are overlapping topics: Martin: Simply because a struct has a constructor does not mean it isn't a viable target/source for use with memcpy/memmove/memset. As the documentation that Seghe

Re: [GSOC] LTO dump tool project

2018-07-10 Thread Hrishikesh Kulkarni
Hi, Thanks for suggestions. I would start working on these points and will try to complete as early as possible. Regards, Hrishikesh On Mon, Jul 9, 2018 at 2:04 PM, Martin Liška wrote: > On 07/09/2018 09:50 AM, Hrishikesh Kulkarni wrote: >> Hi, >> >> The command line option -gimple-stats will

Re: ChangeLog's: do we have to?

2018-07-10 Thread Paul Koning
> On Jul 10, 2018, at 2:18 PM, NightStrike wrote: > > On Fri, Jul 6, 2018 at 1:17 AM, Siddhesh Poyarekar > wrote: >> ... >> >> We had discussed making addition of ChangeLog entries into the commit >> message mandatory but the issue there is that commit logs cannot be (or more >> precisely,

Re: ChangeLog's: do we have to?

2018-07-10 Thread NightStrike
On Fri, Jul 6, 2018 at 1:17 AM, Siddhesh Poyarekar wrote: > On 07/05/2018 05:02 PM, Richard Biener wrote: >> >> I assumed you just want to remove the ChangeLog files, not change >> contents. >> Thus I assumed the commit message would simply contain the ChangeLog >> entry as we requie it today? In

Re: Question on -fopt-info-inline

2018-07-10 Thread Qing Zhao
> On Jul 10, 2018, at 11:32 AM, Richard Biener > wrote: > > On July 10, 2018 5:42:40 PM GMT+02:00, Qing Zhao wrote: >> Hi, David, >> >> thanks a lot for your information. very helpful. >> >> specifically, I am mostly interested in the inline report part of the >> opt-info: >> >> 1. what’s

Re: Question on -fopt-info-inline

2018-07-10 Thread Richard Biener
On July 10, 2018 5:42:40 PM GMT+02:00, Qing Zhao wrote: >Hi, David, > >thanks a lot for your information. very helpful. > >specifically, I am mostly interested in the inline report part of the >opt-info: > >1. what’s the current status of inlining report through opt-info? >(with the upstream GCC

Re: Question on -fopt-info-inline

2018-07-10 Thread Qing Zhao
Hi, David, thanks a lot for your information. very helpful. specifically, I am mostly interested in the inline report part of the opt-info: 1. what’s the current status of inlining report through opt-info? (with the upstream GCC last week, the -fopt-info-inline report nothing) 2. what’s the pl

Re: ChangeLog's: do we have to?

2018-07-10 Thread Siddhesh Poyarekar
On 07/10/2018 08:19 PM, Frank Ch. Eigler wrote: siddhesh wrote: [...] We had discussed making addition of ChangeLog entries into the commit message mandatory but the issue there is that commit logs cannot be (or more precisely, should not be) modified after they're pushed so errors in ChangeL

Re: ChangeLog's: do we have to?

2018-07-10 Thread Frank Ch. Eigler
siddhesh wrote: > [...] We had discussed making addition of ChangeLog entries into the > commit message mandatory but the issue there is that commit logs > cannot be (or more precisely, should not be) modified after they're > pushed so errors in ChangeLog entries will remain. [...] In such a

Re: Are the extended algorithms in the header file going to be supported by gcc ?

2018-07-10 Thread Marco Ippolito
Thanks Thomas for the info. As we can see in https://en.cppreference.com/w/cpp/compiler_support, the support for C++17 parallel algorithms is actually the last major gcc feature for C++17 that needs to be shipped. >From the comments below the report of the last ISO C++ Meeting in Rapperswill : ht

Re: Are the extended algorithms in the header file going to be supported by gcc ?

2018-07-10 Thread Thomas Rodgers
Major GCC releases ship once per year, roughly in May. You can however, today, use the Intel free standing implementation until libstdc++ formally ships with support. See - https://github.com/intel/parallelstl - Tom Marco Ippolito writes: > Hi Thomas, > since simplied and efficient parallelis

Re: Are the extended algorithms in the header file going to be supported by gcc ?

2018-07-10 Thread Marco Ippolito
Hi Thomas, since simplied and efficient parallelism is actually super-needed in a world where fast, simple ed efficient software is paramount, when do you reasonably foresee GCC9 shipping containing the C++17 parallel algorithms? Marco Il giorno lun 21 mag 2018 alle ore 14:32 Thomas Rodgers ha s

Re: Repo conversion troubles.

2018-07-10 Thread Philip Martin
"Eric S. Raymond" writes: > I'm saying I see rsync plus local checkout take 10-12 hours. The rsync is a one-off cost. Once you have the repository locally you can checkout any individual revision much more quickly. I have a local copy of the gcc repository and a checkout of gcc trunk from loca

Making GNU GCC choose_multiplier in expmed.c significantly faster

2018-07-10 Thread colinb2 .
Feel free to copy this email and attachment to anyone who might be interested. I'm very happy to answer any questions anyone has. The program can be compiled and run like this on Linux with GNU GCC: gcc -O2 -o expmed2.exe expmed2.c ./expmed2.exe This email deals with making part of the GNU GCC com

Re: Repo conversion troubles.

2018-07-10 Thread Eric S. Raymond
Jonathan Wakely : > On Tue, 10 Jul 2018 at 09:19, Jonathan Wakely wrote: > > > > On Mon, 9 Jul 2018 at 21:00, Eric S. Raymond wrote: > > > > > > Bernd Schmidt : > > > > On 07/09/2018 09:19 PM, Eric S. Raymond wrote: > > > > > Last time I did a comparison between SVN head and the git conversion >

Re: Good news, bad news on the repository conversion

2018-07-10 Thread Aldy Hernandez
Wait, there's a pot of money for making SVN go away? Sign me up! While we're at it, let's start one for TCL and dejagnu! On Mon, Jul 9, 2018 at 6:58 PM Jeff Law wrote: > > On 07/09/2018 10:53 AM, Janus Weil wrote: > > 2018-07-09 18:35 GMT+02:00 Eric S. Raymond : > >> David Edelsohn : > The t

Re: Repo conversion troubles.

2018-07-10 Thread Jonathan Wakely
On Tue, 10 Jul 2018 at 09:19, Jonathan Wakely wrote: > > On Mon, 9 Jul 2018 at 21:00, Eric S. Raymond wrote: > > > > Bernd Schmidt : > > > On 07/09/2018 09:19 PM, Eric S. Raymond wrote: > > > > Last time I did a comparison between SVN head and the git conversion > > > > tip they matched exactly.

Re: Repo conversion troubles.

2018-07-10 Thread Jonathan Wakely
On Mon, 9 Jul 2018 at 21:00, Eric S. Raymond wrote: > > Bernd Schmidt : > > On 07/09/2018 09:19 PM, Eric S. Raymond wrote: > > > Last time I did a comparison between SVN head and the git conversion > > > tip they matched exactly. This time I have mismatches in the following > > > files. > > > > S

Re: Good news, bad news on the repository conversion

2018-07-10 Thread Jonathan Wakely
On Tue, 10 Jul 2018 at 09:10, Alec Teal wrote: > PS: Migrating what to what? Git. > Wasn't the git migration done years ago? No.

Re: Good news, bad news on the repository conversion

2018-07-10 Thread Jonathan Wakely
On Mon, 9 Jul 2018, 19:05 Paul Smith, wrote: > > On Mon, 2018-07-09 at 10:57 -0600, Jeff Law wrote: > > On 07/09/2018 10:53 AM, Janus Weil wrote: > > > 2018-07-09 18:35 GMT+02:00 Eric S. Raymond : > > > > David Edelsohn : > > > > > > The truth is we're near the bleeding edge of what conventional t

Re: -Wclass-memaccess warning should be in -Wextra, not -Wall

2018-07-10 Thread Marc Glisse
On Mon, 9 Jul 2018, Martin Sebor wrote: My point to all of this (and I'm annoyed that I'm having to repeat it again, as it my first post wasn't clear enough - which it was) was that any programmer using memcpy/memmove/memset is going to know what they're getting into. No, programmers don't alw

Re: Good news, bad news on the repository conversion

2018-07-10 Thread Alec Teal
Is this still an issue? (I missed the convo due to an overzealous spam filter; this is the only message I have) I often use AWS Spot instances (bidding on instances other people previsioned but put up for auction as it's not always needed) to get results extremely quickly without hearing a fa

Re: -Wclass-memaccess warning should be in -Wextra, not -Wall

2018-07-10 Thread Jonathan Wakely
On Tue, 10 Jul 2018, 02:22 Soul Studios wrote: > My point to all of this (and I'm annoyed that I'm having to repeat it > again, as it my first post wasn't clear enough - which it was) was that > any programmer using memcpy/memmove/memset is going to know what they're > getting into. It was clear