bug#7489: [coreutils] over aggressive threads in sort

2010-11-27 Thread Paul Eggert
On 11/26/2010 06:52 PM, Pádraig Brady wrote: > Hmm, seems like multiple threads are racing to update the > static "saved" variable in write_unique() ? I don't think it's as simple as that. write_unique is generating output, and when it is run it is supposed to have exclusive access to the output

bug#7489: [coreutils] over aggressive threads in sort

2010-11-27 Thread Paul Eggert
Following up on my previous email, it appears to me that the following line in mergelines_node is weird: node->dest -= lo_orig - node->lo + hi_orig - node->hi; Surely there should be a "*" in front of that line? (This does not fix the bug; perhaps it is a different bug?)

bug#7502: wc --verbose should say xx lines, yy words, zz characters

2010-11-27 Thread jidanni
Idea: new option: --verbose $ wc --verbose should say xx lines, yy words, zz characters or xx lines yy words zz characters etc. With TAB separator too.

bug#7489: [coreutils] over aggressive threads in sort

2010-11-27 Thread Paul Eggert
Could you please try this little patch? It should fix your problem. I came up with this fix in my sleep (literally! I woke up this morning and the patch was in my head), but haven't had time to look at the code in this area to see if it's the best fix. Clearly there's at least one more bug as no

bug#7489: [coreutils] over aggressive threads in sort

2010-11-27 Thread Pádraig Brady
On 28/11/10 00:57, Paul Eggert wrote: > Could you please try this little patch? It should fix your > problem. I came up with this fix in my sleep (literally! > I woke up this morning and the patch was in my head), but > haven't had time to look at the code in this area to see > if it's the best f

bug#7489: [coreutils] over aggressive threads in sort

2010-11-27 Thread DJ Lucas
On 11/27/2010 06:57 PM, Paul Eggert wrote: > Could you please try this little patch? It should fix your > problem. I came up with this fix in my sleep (literally! > I woke up this morning and the patch was in my head), but > haven't had time to look at the code in this area to see > if it's the b