[Bug other/29442] insn-attrtab has grown too large

2006-10-25 Thread rick at hartmantech dot com


--- Comment #4 from rick at hartmantech dot com  2006-10-25 16:23 ---
The problem is not only confined to sufficiently modern machines. Some of us
have a conservationist sort of outlook, and are happy to find a use for an
older machine as a router, firewall, Kerberos server or whatever. Linux
supports this sort of thing well - a floppy firewall with no hard drive will
run just fine on an 8M machine, and a 486/33 will keep up with all that an
ordinary ADSL connection can transmit. With insn-attrtab excluded, gcc-4.1.1
compiles quickly and well on 52M, and quite possibly on smaller machines,
though I have no very recent experience to prove it. It seems a pity that a
single source file, and an automatically-generated one at that, should
essentially block an excellent compiler from a lot of smaller machines, new and
old, and cause enough of a slowdown even on a 512M machine to arouse concern.

If there is a rational reason for this file to be huge, well and good, but if
it is readily split that would seem like a worthwhile thing to do.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29442



[Bug other/29442] New: insn-attrtab has grown too large

2006-10-12 Thread rick at hartmantech dot com
When compiling gcc-4.1.1, there is at least a serious slowdown, and on many
machines a failure, when insn-attrtab is compiled. There are several threads on
the Gentoo forums about this, some involving machines with 512M of memory. This
file seems to be automatically generated, and has become so large that one user
graphically describes it as a swapfest. Compiling on a machine with the
specified Gentoo minimum of 64M is not practical.

Is it possible to split this file?


-- 
   Summary: insn-attrtab has grown too large
   Product: gcc
   Version: 4.1.1
Status: UNCONFIRMED
  Severity: enhancement
  Priority: P3
 Component: other
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: rick at hartmantech dot com
 GCC build triplet: i686-pc-linux-gnu-4.1.1
  GCC host triplet: i686-pc-linux-gnu-4.1.1
GCC target triplet: i686-pc-linux-gnu-4.1.1


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29442