Re: Converting to LRA (calling all maintainers)
> p.s. Are there plans for converting the SPARC port? The SPARC port has now been converted. Note that the status of the PowerPC port is a bit confusing because both doc/invoke.texi and htdocs/backends.html say that it still uses reload. -- Eric Botcazou
Re: Converting to LRA (calling all maintainers)
From: Eric Botcazou Date: Tue, 03 Jan 2017 22:22:05 +0100 >> p.s. Are there plans for converting the SPARC port? > > The SPARC port has now been converted. Thanks so much for doing this work, I wish I could have been more helpful.
Re: Converting to LRA (calling all maintainers)
On Tue, Jan 3, 2017 at 4:22 PM, Eric Botcazou wrote: >> p.s. Are there plans for converting the SPARC port? > > Note that the status of the PowerPC port is a bit confusing because both > doc/invoke.texi and htdocs/backends.html say that it still uses reload. Fixed. Thanks, David
gcc-5-20170103 is now available
Snapshot gcc-5-20170103 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/5-20170103/ 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-branch revision 244035 You'll find: gcc-5-20170103.tar.bz2 Complete GCC MD5=99cc7c2f9e5b3d623f2db09ac76097a4 SHA1=c684518dfa99902d0e81936cd4de3f19d63ad4a2 Diffs from 5-20161227 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-5 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
Re: Converting to LRA (calling all maintainers)
On 01/03/2017 02:22 PM, Eric Botcazou wrote: p.s. Are there plans for converting the SPARC port? The SPARC port has now been converted. Note that the status of the PowerPC port is a bit confusing because both doc/invoke.texi and htdocs/backends.html say that it still uses reload. Have any back ends been converted since the default was changed, that did not already have LRA support? I looked at this in the context of nios2 a few months ago (when we were still in stage 1) but didn't see an example patch set for any other back end, or a good description of what I needed to do. So I've been lurking waiting for somebody else to be brave enough to go first. :-P Maybe other port maintainers are in the same position? -Sandra
Re: New GCC Mirror
On Fri, 16 Sep 2016, mirr...@letterboxdelivery.org wrote: > We're supporters of your project and have created a mirror. > > Location: Tokyo, Japan > > Mirror: http://gcc.letterboxdelivery.org (http) | > rsync://gcc.letterboxdelivery.org/gcc (rsync) > > Mirror contact email: mirr...@letterboxdelivery.org Thanks for the heads up (and sorry for the delay in getting back to you, I've been "out" for a couple of months last year). I was just going to add your mirror per the patch below, but noticed to issues which are different than our other mirrors: You seem to carry releases only, not snapshots as well, so are not really mirroring the gcc.gnu.org FTP site? And it seems the "recent" GCC 6.3 release is not included yet. Do you have an automated process (that should run at daily or so)? Thanks, Gerald Index: mirrors.html === RCS file: /cvs/gcc/wwwdocs/htdocs/mirrors.html,v retrieving revision 1.237 diff -u -r1.237 mirrors.html --- mirrors.html14 Aug 2016 16:06:14 - 1.237 +++ mirrors.html4 Jan 2017 02:14:41 - @@ -38,6 +38,9 @@ Hungary, Budapest: http://robotlab.itk.ppke.hu/gcc/";>robotlab.itk.ppke.hu, thanks to Adam Rak (neurhlp at gmail.com) Japan: ftp://ftp.dti.ad.jp/pub/lang/gcc/";>ftp.dti.ad.jp, thanks to IWAIZAKO Takahiro (ftp-admin at dti.ad.jp) Japan: http://ftp.tsukuba.wide.ad.jp/software/gcc/";>ftp.tsukuba.wide.ad.jp, thanks to Kohei Takahashi (tsukuba-ftp-servers at tsukuba.wide.ad.jp) +Japan, Tokyo: http://gcc.letterboxdelivery.org";>gcc.letterboxdelivery.org +| rsync://gcc.letterboxdelivery.org/gcc, + thanks to mirr...@letterboxdelivery.org. The Netherlands, Amsterdam: http://nl.mirror.babylon.network/gcc/";>http://nl.mirror.babylon.network/gcc/ | ftp://nl.mirror.babylon.network/gcc/";>ftp://nl.mirror.babylon.network/gcc/ |
Re: Converting to LRA (calling all maintainers)
> Have any back ends been converted since the default was changed, that > did not already have LRA support? I looked at this in the context of > nios2 a few months ago (when we were still in stage 1) but didn't see an > example patch set for any other back end, or a good description of what > I needed to do. The SPARC port fits the description, all the LRA related patches went in starting from December 1st (although the important issues had already been identified and a fair amount of work already been done earlier by Davem). SPARC is a very regular architecture with few, simple addressing modes so the conversion was relatively straightforward. The only irregular feature is the pairing of (even, odd) integer registers in 32-bit mode and it was the source of the annoying issues. I'm going to add a few words on the Wiki about that. -- Eric Botcazou
