Killing old dead bugs

2017-07-02 Thread Yuri Gribov
Hi all, What do I need to do to close an old bug which does not repro with modern GCC and reporter does not care anymore (e.g. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40528)? Also, is there some general policy about closing old bugs? -Y

Re: LCOV of current GCC

2017-07-02 Thread Mikhail Maltsev
Hi all! I noticed that you started to publish GCC test coverage data. About a year ago I also experimented with GCC's coverage and would like to share some possible improvement ideas for your scripts. I postprocess the coverage data with this script: https://gist.github.com/miyuki-chan/943efe7d8e0

Re: Killing old dead bugs

2017-07-02 Thread Mikhail Maltsev
Hi. Yes, bug maintenance is appreciated. See this message and replies to it: https://gcc.gnu.org/ml/gcc/2016-04/msg00258.html . I'm not sure that there is a documented policy, but I might be wrong. -- Regards, Mikhail Maltsev

gcc-8-20170702 is now available

2017-07-02 Thread gccadmin
Snapshot gcc-8-20170702 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/8-20170702/ 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/trunk revision