Re: git-blame segfault

2013-12-03 Thread Antoine Pelisse
On Tue, Dec 3, 2013 at 9:45 AM, Markus Trippelsdorf wrote: > Should be fixed in gcc soon. For the curious, here is the assembler diff > (bad vs. good): Cool, Thanks. Good to know this has nothing to do with Git :-) -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a

Re: git-blame segfault

2013-12-03 Thread Markus Trippelsdorf
On 2013.12.02 at 16:05 +0100, Markus Trippelsdorf wrote: > On 2013.12.02 at 15:15 +0100, Antoine Pelisse wrote: > > Would that mean that gcc is doing some steps in the wrong order ? That > > is setting xecfg.hunk_func and then emptying the structure ? I've > > already had a similar bug, but that's

Re: git-blame segfault

2013-12-02 Thread Markus Trippelsdorf
On 2013.12.02 at 15:15 +0100, Antoine Pelisse wrote: > On Mon, Dec 2, 2013 at 1:57 PM, Markus Trippelsdorf > wrote: > > When git is compiled with current gcc and "-march=native" > > git-blame segfaults: > > > > For example: > > > > % gdb --args /var/tmp/git/git-blame gcc/tree-object-size.c > > ..

Re: git-blame segfault

2013-12-02 Thread Antoine Pelisse
On Mon, Dec 2, 2013 at 1:57 PM, Markus Trippelsdorf wrote: > When git is compiled with current gcc and "-march=native" > git-blame segfaults: > > For example: > > % gdb --args /var/tmp/git/git-blame gcc/tree-object-size.c > ... > Program received signal SIGSEGV, Segmentation fault. > 0x00

git-blame segfault

2013-12-02 Thread Markus Trippelsdorf
When git is compiled with current gcc and "-march=native" git-blame segfaults: For example: % gdb --args /var/tmp/git/git-blame gcc/tree-object-size.c ... Program received signal SIGSEGV, Segmentation fault. 0x in ?? () (gdb) bt #0 0x in ?? () #1 0x0051