This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug c++/12256] virtual memory exhausted: Invalid argument


PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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



------- Additional Comments From raimond_merkert at raytheon dot com  2003-09-13 13:57 -------
I've also run into this problem. I thought it had something to do with
-finline-functions, because when I took it out it worked. I tried to file a
report with the preprocessed source, but unfortunately that seemed to compile
fine (so I thought my memory mightbe corrupt). I actually ran 'top' while the
compiler was running and I did not see it use up much memory at all (unless it
made a request for a huge block of memory). Using different inline-limits (eg.
100) did not work either.

I think this may have been introduced last week, because I had no problems
compiling with the 2003-09-03 (I think it was) release.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]