On Wed, Oct 02, 2013 at 07:14:24PM +0200, Torbjorn Granlund wrote:
>
> It sounds a lot like David Harvey's and my tool, which we call the
> "loopmixer". We never wrote it neatly enough for public release, but
> we've used it for the last 4 years or so for tweaking the assembly code
> of GMP. (
On Wed, Oct 02, 2013 at 08:19:29PM +0200, Niels Möller wrote:
> Torbjorn Granlund writes:
>
> > We don't handle alternatives currently, except with a loop around the
> > loopmixer. One could think of several classes, some known to the tool,
> > others not-always-valid only by source file annotat
On Thu, Sep 26, 2013 at 09:20:29PM +0200, Torbjorn Granlund wrote:
> For the last few months, I have been working on writing and rewriting
> basecase code for X64-64 processors. The result is now in the
> mainline GMP repo.
>
I am writing a tool that might be useful, a simple optimizer of assembl
On Sun, Jul 21, 2013 at 10:44:41PM +0200, Marc Glisse wrote:
> On Sun, 21 Jul 2013, Ondřej Bílka wrote:
>
> >One of things that benefit from economy of scale is fixing typos. Below
> >is patch that fixes 99 typos and it was fast to generate.
>
> "coproccessor"
Hi,
One of things that benefit from economy of scale is fixing typos. Below
is patch that fixes 99 typos and it was fast to generate.
This is part of project that I am writing
https://github.com/neleai/stylepp
whose aim is to effectively solve various issues.
A method that I used is following:
On Tue, Jul 09, 2013 at 02:28:37PM +0200, Torbjorn Granlund wrote:
> Ondřej Bílka writes:
>
> Are leading ws all spaces or tabs followed by less than 8 spaces?
>
> That's probably what we usually do.
>
> Are there some form-feeds and are they useful?
>
>
Hi,
I am writing tool to help with various style issues. This will
simplify code review as these issues will be solved automatically.
As prerequisite I need to have to start with consistent codebase.
It is possible to fix only files that are touched by commit but this can
introduce unrelated chan
