Argument Against Removal of GCJ

2017-02-21 Thread R0b0t1
I have found GCJ to be one of the best methods for bootstrapping OpenJDK. No other method of adding support for new architectures that does not involve working closely with OpenJDK upstream is known to me. It is, of course, possible to add any architecture without the use of GCJ, but if one wishes

gcc-5-20170221 is now available

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

Re: Obsolete powerpc*-*-*spe*

2017-02-21 Thread David Edelsohn
On Mon, Feb 20, 2017 at 11:02 AM, Olivier Hainque wrote: > Hi David, > >> On Feb 17, 2017, at 01:10 , David Edelsohn wrote: >> >> This is not a new issue. The maintainer did not suddenly resign last >> week. There have been numerous efforts to reach out to the SPE >> community for over a *decad

Re: Disable -std=c++17 "ISO C++1z does not allow dynamic exception specifications"?

2017-02-21 Thread Stephan Bergmann
On 02/21/2017 03:56 PM, Jonathan Wakely wrote: On 21 February 2017 at 14:55, Jonathan Wakely wrote: On 21 February 2017 at 14:51, Jakub Jelinek wrote: On Tue, Feb 21, 2017 at 03:44:17PM +0100, Stephan Bergmann wrote: There is no flag to suppress that error or demote it to a warning, is there?

Re: Disable -std=c++17 "ISO C++1z does not allow dynamic exception specifications"?

2017-02-21 Thread Jonathan Wakely
On 21 February 2017 at 14:51, Jakub Jelinek wrote: > On Tue, Feb 21, 2017 at 03:44:17PM +0100, Stephan Bergmann wrote: >> There is no flag to suppress that error or demote it to a warning, is there? >> Could be useful when adapting large code bases to C++17 incrementally. > > It is a warning in C++

Re: Disable -std=c++17 "ISO C++1z does not allow dynamic exception specifications"?

2017-02-21 Thread Jonathan Wakely
On 21 February 2017 at 14:55, Jonathan Wakely wrote: > On 21 February 2017 at 14:51, Jakub Jelinek wrote: >> On Tue, Feb 21, 2017 at 03:44:17PM +0100, Stephan Bergmann wrote: >>> There is no flag to suppress that error or demote it to a warning, is there? >>> Could be useful when adapting large cod

Disable -std=c++17 "ISO C++1z does not allow dynamic exception specifications"?

2017-02-21 Thread Stephan Bergmann
There is no flag to suppress that error or demote it to a warning, is there? Could be useful when adapting large code bases to C++17 incrementally.

Re: Disable -std=c++17 "ISO C++1z does not allow dynamic exception specifications"?

2017-02-21 Thread Jakub Jelinek
On Tue, Feb 21, 2017 at 03:44:17PM +0100, Stephan Bergmann wrote: > There is no flag to suppress that error or demote it to a warning, is there? > Could be useful when adapting large code bases to C++17 incrementally. It is a warning in C++11/C++14 now, so compile with -std=c++14 and incrementally

Install of gcc-plugin-devel

2017-02-21 Thread Tuende Erdei
Hi, we have to analyse a C++ code that show significant run time overhead through the scorep instrumentation. Therefore we want to use the compile time filtering to get reasonable results. If I understand correctly, scorep need the GCC plugin interface to have the compile time filtering and I