[Bug target/33120] Large module object files when declare arrays on Mac OSX
--- Comment #5 from meihome at gmail dot com 2008-10-08 14:28 --- FORTRAN Unit Testing Framework (Fruit) 2.5 is released. The pre-fixed message of 30 is not a dynamic allocated array. The problem should be solved. The project site is: http://fortranxunit.wiki.sourceforge.net/ -- meihome at gmail dot com changed: What|Removed |Added CC||meihome at gmail dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33120
[Bug target/33120] Large module object files when declare arrays on Mac OSX
--- Comment #6 from meihome at gmail dot com 2008-10-08 15:35 --- Sorry, the previous fruit_2.5.zip was not tested under gfortran. Please use the new fruit_2.5.1.zip. That corrected the 450MB file problem, and compiled under gfortran. https://sourceforge.net/project/platformdownload.php?group_id=152125sel_platform=6415 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33120
[Bug target/33120] Large module object files when declare arrays on Mac OSX
--- Comment #7 from meihome at gmail dot com 2008-10-08 16:43 --- Sorry for keep on updating this bug report. Fruit 2.6 is now tested and run with gfortran. The rake build system also works. Download and information here: http://fortranxunit.wiki.sourceforge.net/ -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33120
[Bug target/33120] Large module object files when declare arrays on Mac OSX
--- Comment #3 from johnson at cs dot uiuc dot edu 2008-10-07 02:58 --- Created an attachment (id=16469) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16469action=view) fruit.f90, illustrates huge .o file, requires fruit_util.f90 I think I have a testcase that shows this bug. I was trying to compile FRUIT on my Mac and discovered that fruit.o was 450MB! I am attaching fruit.f90 and fruit_util.f90. I had to modify fruit.f90 a little bit to make it compile; I just added a pair of matching parentheses to two lines. So I figured I should attach the files instead of pointing to them. Ralph Johnson - [EMAIL PROTECTED] -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33120
[Bug target/33120] Large module object files when declare arrays on Mac OSX
--- Comment #4 from johnson at cs dot uiuc dot edu 2008-10-07 02:58 --- Created an attachment (id=16470) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16470action=view) fruit_util.f90, needed to compile fruit.f90 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33120
[Bug target/33120] Large module object files when declare arrays on Mac OSX
--- Comment #2 from dave dot allured at noaa dot gov 2008-10-02 00:32 --- Confirmed this problem for gcc 4.3.1 on Mac OS 10.5.5. A workaround, and recommended best practice for new code, is to make arrays in modules allocatable, i.e. don't declare statically dimensioned large arrays. Then you must add allocate statements at the appropriate initialization locations. This is a problem for legacy fortran 90+ code because adding code for dynamic allocation can spawn bugs. The preferred solution is that uninitialized variables should never occupy physical space in object files. My thanks to whomever can work on this fix. --Dave A. -- dave dot allured at noaa dot gov changed: What|Removed |Added CC||dave dot allured at noaa dot ||gov http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33120
[Bug target/33120] Large module object files when declare arrays on Mac OSX
--- Comment #1 from tobi at gcc dot gnu dot org 2007-10-07 19:52 --- Probably more of a target issue than a frontend issue. Please push back to the frontend with an explanation what the FE is doing wrong if the backend does the right thing. -- tobi at gcc dot gnu dot org changed: What|Removed |Added CC||tobi at gcc dot gnu dot org Component|fortran |target GCC target triplet||i386-darwin http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33120
