This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: A branch for 256bit vectorizer

From: Jason Merrill <jason at redhat dot com>
To: "H.J. Lu" <hjl dot tools at gmail dot com>
Cc: Richard Guenther <richard dot guenther at gmail dot com>, GCC Development <gcc at gcc dot gnu dot org>, Bernie Innocenti <bernie at codewiz dot org>
Date: Tue, 11 May 2010 10:49:08 -0400
Subject: Re: A branch for 256bit vectorizer
References: <AANLkTiltLP3Wic5Km0ldCKb0oJt5GlmTsZ4uqoSfbhXb@mail.gmail.com>

On 05/11/2010 10:30 AM, H.J. Lu wrote:

I created a branch for 256bit vectorizer, branches/vect256/.  Richard
and I will work on it to extend vectorizer to 256bit.

Jason, can you include it in git mirror? We can drop the ix86 branch
in git since there are several branches under branches/ix86.

It's already mirrored, just not one that is included in the default clone. Assuming you have a clone like that described in http://gcc.gnu.org/wiki/GitMirror, you would say

git config --add remote.origin.fetch refs/remotes/vect256:refs/remotes/origin/vect256 git config --add svn-remote.svn.fetch branches/vect256:refs/remotes/origin/vect256

and you should be all set.

I did drop the ix86 branch, as the git-svn subdirectory confusion significantly increases the overhead from including it in the clone set.

Jason

Follow-Ups:
- Re: A branch for 256bit vectorizer
  - From: H.J. Lu

References:
- A branch for 256bit vectorizer
  - From: H.J. Lu

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]