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++/12252] ICE on very large source file : GC problem?


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

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



------- Additional Comments From ebotcazou at gcc dot gnu dot org  2003-09-14 07:07 -------
Here's a tip from our resident GC expert:

> The best way to start investigating a GC problem is to use
> --param ggc-min-heapsize=0 --param ggc-min-expand=0
> which will force garbage collection to happen every time it can.
> This should make the problem reproducible and make it easier to produce
> a cut-down testcase.

He also said that GC problems are safely fixable on a release branch, so if you
can trim down your testcase and post it here, I'll investigate.


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