Re: Moving to git

On Thu, Aug 20, 2015 at 04:09:39PM -0400, Jason Merrill wrote: > On 08/20/2015 02:23 PM, Jeff Law wrote: > >I suspect Jakub will strongly want to see some kind commit hook to > >associate something similar to an SVN id to each git commit to support > >his workflow where the SVN ids are associated

Re: Moving to git

Jakub Jelinek writes: > And for those really identifying them by sha1 hashes is significantly > worse than using monotonically increasing small number, sha1 hashes > are impossible to remember, and you don't know what is earlier and > what is later from just looking at it. git describe gives you

Re: Moving to git

On 24 August 2015 at 09:17, Jakub Jelinek wrote: > The revision ids are also useful for bugzilla, r123456 > links in text pointing to http://gcc.gnu.org/r123456 is significantly > shorter The first six characters of the sha1 is usually enough to unambiguously identify a commit, so we could easily

Re: Moving to git - bibisect ...

Hi Jakub, On Mon, 2015-08-24 at 10:17 +0200, Jakub Jelinek wrote: > > Jakub: How about using git bisect instead, and identify the compiler > > binaries with the git commit sha1? > > That is really not useful. While you speed it bisection somewhat by avoiding > network traffic and communication w

Re: Moving to git

Jonathan Wakely : > On 24 August 2015 at 09:17, Jakub Jelinek wrote: > > The revision ids are also useful for bugzilla, r123456 > > links in text pointing to http://gcc.gnu.org/r123456 is significantly > > shorter > > The first six characters of the sha1 is usually enough to > unambiguously identi

Re: Moving to git

On 24 August 2015 at 11:42, Eric S. Raymond wrote: > Jonathan Wakely : >> On 24 August 2015 at 09:17, Jakub Jelinek wrote: >> > The revision ids are also useful for bugzilla, r123456 >> > links in text pointing to http://gcc.gnu.org/r123456 is significantly >> > shorter >> >> The first six characte

Re: Offer of help with move to git

Eric> In the mean time, I'm enclosing a contributor map that will need to be Eric> filled in whoever does the conversion. The right sides should become Eric> full names and preferred email addresses. It's probably worth starting with the map I used when converting gdb. There is a lot of overlap b

Re: Moving to git

On 24/08/15 12:43, Jonathan Wakely wrote: > On 24 August 2015 at 11:42, Eric S. Raymond wrote: >> Jonathan Wakely : >>> On 24 August 2015 at 09:17, Jakub Jelinek wrote: The revision ids are also useful for bugzilla, r123456 links in text pointing to http://gcc.gnu.org/r123456 is significa

Re: Offer of help with move to git

On Sun, 23 Aug 2015, Eric S. Raymond wrote: > Whoever you designate to lead the conversion *should read this Jason Merrill is leading the conversion. > Hwew's a particular warning: though you may be using git-svn for live > gatewaying, it is *not* the way to go for full-history conversions, as

Re: Offer of help with move to git

On Sun, 23 Aug 2015, Andreas Schwab wrote: > Florian Weimer writes: > > > Okay, it's not a big deal for me if my older contributions are > > attributed to Red Hat. I was just wondering. > > Since subversion doesn't store author names, only committer names, the > real attributions are in the Ch

Re: Offer of help with move to git

Tom Tromey : > Eric> In the mean time, I'm enclosing a contributor map that will need to be > Eric> filled in whoever does the conversion. The right sides should become > Eric> full names and preferred email addresses. > > It's probably worth starting with the map I used when converting gdb. > Th

Re: Moving to git

On 08/24/2015 02:17 AM, Jakub Jelinek wrote: On Thu, Aug 20, 2015 at 04:09:39PM -0400, Jason Merrill wrote: On 08/20/2015 02:23 PM, Jeff Law wrote: I suspect Jakub will strongly want to see some kind commit hook to associate something similar to an SVN id to each git commit to support his workf

Re: Moving to git

On Mon, Aug 24, 2015 at 09:34:41AM -0600, Jeff Law wrote: > On 08/24/2015 02:17 AM, Jakub Jelinek wrote: > >On Thu, Aug 20, 2015 at 04:09:39PM -0400, Jason Merrill wrote: > >>On 08/20/2015 02:23 PM, Jeff Law wrote: > >>>I suspect Jakub will strongly want to see some kind commit hook to > >>>associa

Re: Moving to git

On 08/24/2015 09:43 AM, Jakub Jelinek wrote: On Mon, Aug 24, 2015 at 09:34:41AM -0600, Jeff Law wrote: On 08/24/2015 02:17 AM, Jakub Jelinek wrote: On Thu, Aug 20, 2015 at 04:09:39PM -0400, Jason Merrill wrote: On 08/20/2015 02:23 PM, Jeff Law wrote: I suspect Jakub will strongly want to see

Re: Moving to git

On 24/08/15 16:43, Jakub Jelinek wrote: > On Mon, Aug 24, 2015 at 09:34:41AM -0600, Jeff Law wrote: >> On 08/24/2015 02:17 AM, Jakub Jelinek wrote: >>> On Thu, Aug 20, 2015 at 04:09:39PM -0400, Jason Merrill wrote: On 08/20/2015 02:23 PM, Jeff Law wrote: > I suspect Jakub will strongly wan

Power ELFv2 ABI now openly published

At Cauldron this year, several people complained to me that our latest ABI document was behind a registration wall. I'm happy to say that we've finally gotten past the issues that were holding it there, and it is now openly available at: https://members.openpowerfoundation.org/document/dl/576

Re: Offer of help with move to git

Joseph Myers : > Hence my suggestion in > of reconverting and then combining with the existing git-svn history via > renaming all the refs in the existing git repository, so as to preserve > the validity of commit references and git-only branche

Re: Moving to git

On Mon, 24 Aug 2015, Jakub Jelinek wrote: > Not to mention we should keep the existing r123456 comments in bugzilla > working, and I'm not convinced keeping a SVN version of the repository > (frozen) for that purpose is the best idea. Of course you keep the SVN repository there indefinitely, read

Re: Offer of help with move to git

On Mon, 24 Aug 2015, Eric S. Raymond wrote: > Joseph Myers : > > Hence my suggestion in > > of reconverting and then combining with the existing git-svn history via > > renaming all the refs in the existing git repository, so as to preserve > >

Re: Moving to git

On Mon, Aug 24, 2015 at 10:22:22AM +0200, Andreas Schwab wrote: > Jakub Jelinek writes: > > > And for those really identifying them by sha1 hashes is significantly > > worse than using monotonically increasing small number, sha1 hashes > > are impossible to remember, and you don't know what is ea

porting to lra

are there any guidelines as to what needs to be done in the backend to enable lra for 5.2? when I turn it on I get two types of errors. 1) insn not recognized because fp hasn't been converted yet, and 2) max number of generated reload insns. any pointers will be appreciated shmeel

Re: Offer of help with move to git

Joseph Myers : > FWIW, Jason's own trial conversion with reposurgeon got up to at least > 45GB memory consumption on a 32GB repository. I have no trouble believing that at *all*. -- http://www.catb.org/~esr/";>Eric S. Raymond

Re: porting to lra

On 08/24/2015 02:43 PM, shmeel gutl wrote: are there any guidelines as to what needs to be done in the backend to enable lra for 5.2? Unfortunately, switching from reload to LRA can be a difficult task. Reload pass is driven by many machine target hooks. As LRA uses different algorithms these

Re: Moving to git

Jakub Jelinek writes: > But it is not unique across different branches, and furthermore, what is the > fast way to go from the number to a commit? The git describe output is a valid ref by itself. Andreas. -- Andreas Schwab, SUSE Labs, sch...@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970

Re: Offer of help with move to git

Joseph Myers writes: > [...] > FWIW, Jason's own trial conversion with reposurgeon got up to at least > 45GB memory consumption on a 32GB repository. (The host sourceware.org box has 72GB.) - FChE

Re: Offer of help with move to git

On 08/24/2015 01:46 PM, Frank Ch. Eigler wrote: Joseph Myers writes: [...] FWIW, Jason's own trial conversion with reposurgeon got up to at least 45GB memory consumption on a 32GB repository. (The host sourceware.org box has 72GB.) And if Jason really needs it, we've got considerably larger

Re: CFI directives and dynamic stack alignment

On Tue, 2015-08-18 at 09:23 +0930, Alan Modra wrote: > On Mon, Aug 17, 2015 at 10:38:22AM -0700, Steve Ellcey wrote: > OK, then you need to emit a .cfi directive to say the frame top is > given by the temp hard reg sometime after that assignment and before > sp is aligned in the prologue, and anot