[Bug other/18623] 4 * libiberty local variables set but never used

2004-11-23 Thread ian at wasabisystems dot com

--- Additional Comments From ian at wasabisystems dot com  2004-11-24 02:10 
---
I'll take demangler issues.

-- 
   What|Removed |Added

 AssignedTo|unassigned at gcc dot gnu   |ian at airs dot com
   |dot org |
 Status|NEW |ASSIGNED


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


[Bug c/12245] [3.4.3/4.0.0 regression] Uses lots of memory when compiling large initialized arrays

2004-12-02 Thread ian at wasabisystems dot com

--- Additional Comments From ian at wasabisystems dot com  2004-12-02 15:53 
---
I attached a simple test case.  This is based on real existing code, although I
changed all the values to hide potentially proprietary information.  When I
compile this file without optimization, it uses some 200M, and garbage collects
while compiling this file.  The compilation takes 1 minutes, 45 seconds.  (This
is much better than gcc 3.4.3, actually, which used all available memory,
garbage collected twice, and wound up swapping for 10 minutes or so before
completing).

When compiling with 2.95.3, the compiler uses 20M and completes in 37 seconds.

The compiler used to work fine when processing very large initializers.  As it
read the initializer, gcc would output the initializer to the assembler file
directly.  This capability was removed here:
http://gcc.gnu.org/ml/gcc-patches/2000-10/msg00933.html
The followups to that message mention this type of problem.

-- 
   What|Removed |Added

  Known to fail||3.4.3 4.0.0
  Known to work||2.95.3
Summary|Crashes when compiling large|[3.4.3/4.0.0 regression]
   |initialized arrays  |Uses lots of memory when
   ||compiling large initialized
   ||arrays


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


[Bug bootstrap/18895] libgfortran AM_MAKEFLAGS arg list + environment too large

2004-12-08 Thread ian at wasabisystems dot com

--- Additional Comments From ian at wasabisystems dot com  2004-12-09 05:17 
---
Here is my analysis:
http://gcc.gnu.org/ml/gcc-patches/2004-12/msg00659.html

My conclusion is that if you are using GNU make 3.79 or above, as is required by
the gcc installation instructions, there is no need to set AM_MAKEFLAGS in the
libgfortran Makefile.


-- 


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