On May 3, 2012, at 9:31 AM, Steven Bosscher wrote:
> How does one turn random volunteer GCC hackers into spoiled brats?
So, brats aside, your new patch breaks my port...
diff --git a/gcc/Makefile.in b/gcc/Makefile.in
index 145e8b8..1eeeab9 100644
--- a/gcc/Makefile.in
+++ b/gcc/Makefile.in
@@ -35
On 05/04/12 06:54, Steven Bosscher wrote:
> Attached is another attempt. It's a much larger patch because I've now
> had to change all write_* functions in genattrtab.c to pass around a
> FILE pointer. But it's not a gross as the first attempt. Hopefully you
> agree :-)
I do agree!
> Bootstrapped
On 05/03/2012 09:31 AM, Steven Bosscher wrote:
+/* This gen* file is unique, in that it writes out multiple files.
+
+ Before GCC 4.8, insn-attrtab.c was written out containing many large
+ functions and tables. This made insn-attrtab.c_the_ bottle-neck in
+ a parallel build, and even mad
On May 3, 2012, at 9:31 AM, Steven Bosscher wrote:
> How does one turn random volunteer GCC hackers into spoiled brats?
> Give them Big Iron to play with, like IBM's donation to the compile
> farm aka gcc110. If you do "make -k 64" on a machine like that, a GCC
> build takes _minutes_, and that's s
Hello,
How does one turn random volunteer GCC hackers into spoiled brats?
Give them Big Iron to play with, like IBM's donation to the compile
farm aka gcc110. If you do "make -k 64" on a machine like that, a GCC
build takes _minutes_, and that's so slooow...
Part of the problem is insn-at
