This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/25647] Large automaticallty generated code (unrolled loop) crashes the compiler
- From: "jonas dot mellin at his dot se" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 12 Mar 2006 19:58:16 -0000
- Subject: [Bug c++/25647] Large automaticallty generated code (unrolled loop) crashes the compiler
- References: <bug-25647-11959@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #4 from jonas dot mellin at his dot se 2006-03-12 19:58 -------
(In reply to comment #3)
> Your compiler simply runs out of memory.
The compiler gives an error message to leave a message on bugzilla when it runs
out of memory instead of saying that it ran out of memory. I gathered this from
some simple experiments. So, my complaint is really about the error messages
from the compiler itself.
> Don't do code like this. It will
> also not be very efficient.
I want to get rid of the effect of the instruction cache in the hardware to
obtain a baseline to demonstrate the effect of the instruction cache in
measurements. So, I do not really care about efficiency, or rather I care a lot
about it.
>
> W.
>
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25647