Re: is it time to mass change from .c to .cc in gcc/ ?

On Tue, Apr 14, 2015 at 10:46:19AM +0200, Richard Biener wrote: > On Tue, Apr 14, 2015 at 7:20 AM, Trevor Saunders > wrote: > > Hi! > > > > To be clear I only want to talk about gcc/**/*.c but *not* testsuite/ > > > > The Question of changing from .c to a more standard C++ file extension > > has

gcc-5-20150414 is now available

Snapshot gcc-5-20150414 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/5-20150414/ 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: Fail to compile trunk

On 14 April 2015 at 17:19, Harald Servat wrote: > Should we file a PR to request to integrate this patch? Or should I > better follow Peter's suggestion to build gcc from a separate build > directory? You should always build in a separate directory, that's what all the installation docs and the FA

Re: Fail to compile trunk

This is already filed as PR65763. Andreas. -- Andreas Schwab, SUSE Labs, sch...@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."

Re: Fail to compile trunk

That patch solved the problem Andreas, thank you very much! Should we file a PR to request to integrate this patch? Or should I better follow Peter's suggestion to build gcc from a separate build directory? Best regards. 2015-04-14 18:14 GMT+02:00 Andreas Schwab : > Please try this patch: > > di

Re: Fail to compile trunk

Ah, sorry for the misundersanding, I'll send the questions to gcc-help from now on! Still, thank you very much for the answer! 2015-04-14 18:14 GMT+02:00 Peter Bergner : > On Tue, 2015-04-14 at 17:37 +0200, Harald Servat wrote: >> I'm trying to compile the GCC's trunk but I find out the followi

Re: Fail to compile trunk

Please try this patch: diff --git a/libcc1/Makefile.am b/libcc1/Makefile.am index ecab22c..7a274b3 100644 --- a/libcc1/Makefile.am +++ b/libcc1/Makefile.am @@ -17,7 +17,7 @@ ## . ACLOCAL_AMFLAGS = -I .. -I ../config -gcc_build_dir = ../$(host_subdir)/gcc +gcc_buil

Re: Fail to compile trunk

On Tue, 2015-04-14 at 17:37 +0200, Harald Servat wrote: > I'm trying to compile the GCC's trunk but I find out the following > error while compiling it. I've configured it such as This question is not appropriate for this mailing list, as this list is only for questions about gcc development. Y

Fail to compile trunk

Hello, I'm trying to compile the GCC's trunk but I find out the following error while compiling it. I've configured it such as ./configure --prefix=/home/harald/pkg/gcc/git --enable-languages=c,c++ --disable-multilib and then run the make using the parallel build using 4 simultaneous jobs

Re: is it time to mass change from .c to .cc in gcc/ ?

On Tue, Apr 14, 2015 at 7:20 AM, Trevor Saunders wrote: > Hi! > > To be clear I only want to talk about gcc/**/*.c but *not* testsuite/ > > The Question of changing from .c to a more standard C++ file extension > has come up a couple times. I believe its reasonable accurate to say > the consensus

Re: About adding OMPT into GNU's libgomp

2015-04-13 12:53 GMT+02:00 Jakub Jelinek : > > The only thing I'd like to say is that it would be nice if the changes > didn't affect performance of non-analyzed/traced apps, so if changes to hot > code paths are needed, they should be done with care, guarded with > __builtin_expect and benchmarked

Re: lto bootstrap fails.

On Mon, 13 Apr 2015, Jakub Jelinek wrote: > On Mon, Apr 13, 2015 at 05:46:35PM +0200, Toon Moene wrote: > > [ Patch elided ] > > > > The patch applied cleanly - this is what I got as a result: > > > > https://gcc.gnu.org/ml/gcc-testresults/2015-04/msg01450.html > > > > I hope this is useful. >

Re: Connecting to gcc.gnu.org - keygen_fail

14.04.2015 9:28, j...@aptnsw.org.au writes: > Hi, > > If I try to browse to pages like http://gcc.gnu.org/bugs/segfault.html I get > the following Mozilla alert: > >> >> An error occurred during a connection to gcc.gnu.org:443. Unable to >> generate public/private key pair. (Error code: sec_