Re: Fixing cvs2svn branchpoints

2019-11-01 Thread Joseph Myers
And here are corresponding lists of tags where the commit cvs2svn generated for the tag should be reparented. The semantics are exactly the same as for branches (change the parent of that commit without changing the tree contents). In many but not all cases, the reparenting may result in the

gcc-8-20191101 is now available

2019-11-01 Thread gccadmin
Snapshot gcc-8-20191101 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/8-20191101/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 8 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-8

GCC's instrumentation and the target environment

2019-11-01 Thread David Taylor
I wish to use GCC based instrumentation on an embedded target. And I am finding that GCC's libgcov.a is not well suited to my needs. Ideally, all the application entry points and everthing that knows about the internals of the implementation would be in separate files from everything that does i/

Re: Fixing cvs2svn branchpoints

2019-11-01 Thread Joseph Myers
On Fri, 1 Nov 2019, Eric S. Raymond wrote: > Joseph Myers : > > Here are complete lists of reparentings I think should be done on the > > commits that start branches, along with my notes on branches with messy > > initial commits but where I don't think any reparenting should be done. > > The

Re: GCC 10.0 Status Report (2019-10-22), Stage 1 to end Nov 16th

2019-11-01 Thread Marek Polacek
On Fri, Nov 01, 2019 at 09:31:07AM -0600, Jeff Law wrote: > On 11/1/19 9:08 AM, Marek Polacek wrote: > > On Fri, Nov 01, 2019 at 04:01:12PM +0100, Romain Geissler wrote: > >> Le mar. 22 oct. 2019 à 14:53, Richard Biener a écrit : > >>> > >>> Please make sure to get features intended for GCC 10 fin

Re: GCC 10.0 Status Report (2019-10-22), Stage 1 to end Nov 16th

2019-11-01 Thread Jeff Law
On 11/1/19 9:08 AM, Marek Polacek wrote: > On Fri, Nov 01, 2019 at 04:01:12PM +0100, Romain Geissler wrote: >> Le mar. 22 oct. 2019 à 14:53, Richard Biener a écrit : >>> >>> Please make sure to get features intended for GCC 10 finished >>> and reviewed before the end of stage 1. >>> >> >> Hi, >> >

Re: GCC 10.0 Status Report (2019-10-22), Stage 1 to end Nov 16th

2019-11-01 Thread Marek Polacek
On Fri, Nov 01, 2019 at 04:01:12PM +0100, Romain Geissler wrote: > Le mar. 22 oct. 2019 à 14:53, Richard Biener a écrit : > > > > Please make sure to get features intended for GCC 10 finished > > and reviewed before the end of stage 1. > > > > Hi, > > I understand my question comes very (most li

Re: GCC 10.0 Status Report (2019-10-22), Stage 1 to end Nov 16th

2019-11-01 Thread Romain Geissler
Le mar. 22 oct. 2019 à 14:53, Richard Biener a écrit : > > Please make sure to get features intended for GCC 10 finished > and reviewed before the end of stage 1. > Hi, I understand my question comes very (most likely too) late, but are there any plans to switch the default C++ dialect to -std=g