Re: Official GCC git repository

>> git config --add remote.origin.fetch '+refs/remotes/*:refs/remotes/*' > > This will put the remote branch heads in refs/remotes, you might want to > put them in refs/remotes/origin instead. > > $ git config --add remote.origin.fetch '+refs/remotes/*:refs/remotes/origin/*' One small problem I ha

Makefile support requested - enabling multilib for target

Currently, gcc doesn't support a multilib build for win64. I have been looking at how to do this, and have so far come up with a beginning to a solution. The work done thus far is part of this PR: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38294 The current blocker is in building libgcc. At s

Re: GCC 4.4.0 Status Report (2008-11-27)

On Tue, 9 Dec 2008, Jeff Law wrote: > Hans-Peter Nilsson wrote: > > Vladimir, have you had chance to look at supporting > > LOAD_EXTEND_OP (implicit sign-extension) in IRA? > > > > > > > > I'm guessing no, but hope it's not forgotten. > > > > I inte

Re: Official GCC git repository

Rafael Espindola wrote: >>> git config --add remote.origin.fetch '+refs/remotes/*:refs/remotes/*' >> This will put the remote branch heads in refs/remotes, you might want to >> put them in refs/remotes/origin instead. >> >> $ git config --add remote.origin.fetch >> '+refs/remotes/*:refs/remotes/or