public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
* [Bug c++/25647] New: Large automaticallty generated code (unrolled loop) crashes the compiler
@ 2006-01-03 8:01 jonas dot mellin at his dot se
2006-01-03 8:03 ` [Bug c++/25647] " jonas dot mellin at his dot se
` (3 more replies)
0 siblings, 4 replies; 5+ messages in thread
From: jonas dot mellin at his dot se @ 2006-01-03 8:01 UTC (permalink / raw)
To: gcc-bugs
Large automatically generated code (unrolled bubble sort) on std::vector<int>
crashes the compiler. If there are 1000 elements in the vector, the compiler
crashes with the message:
g++ ur1000.cc -o ur1000.exe
ur1000.cc: In function `int main(int, char**)':
ur1000.cc:99799: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
--
Summary: Large automaticallty generated code (unrolled loop)
crashes the compiler
Product: gcc
Version: 3.4.4
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: jonas dot mellin at his dot se
GCC host triplet: i686-pc-cygwin
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25647
^ permalink raw reply [flat|nested] 5+ messages in thread* [Bug c++/25647] Large automaticallty generated code (unrolled loop) crashes the compiler 2006-01-03 8:01 [Bug c++/25647] New: Large automaticallty generated code (unrolled loop) crashes the compiler jonas dot mellin at his dot se @ 2006-01-03 8:03 ` jonas dot mellin at his dot se 2006-02-14 4:10 ` pinskia at gcc dot gnu dot org ` (2 subsequent siblings) 3 siblings, 0 replies; 5+ messages in thread From: jonas dot mellin at his dot se @ 2006-01-03 8:03 UTC (permalink / raw) To: gcc-bugs ------- Comment #1 from jonas dot mellin at his dot se 2006-01-03 08:03 ------- Created an attachment (id=10577) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10577&action=view) The code generating the erroneous code -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25647 ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug c++/25647] Large automaticallty generated code (unrolled loop) crashes the compiler 2006-01-03 8:01 [Bug c++/25647] New: Large automaticallty generated code (unrolled loop) crashes the compiler jonas dot mellin at his dot se 2006-01-03 8:03 ` [Bug c++/25647] " jonas dot mellin at his dot se @ 2006-02-14 4:10 ` pinskia at gcc dot gnu dot org 2006-03-08 5:14 ` bangerth at dealii dot org 2006-03-12 19:58 ` jonas dot mellin at his dot se 3 siblings, 0 replies; 5+ messages in thread From: pinskia at gcc dot gnu dot org @ 2006-02-14 4:10 UTC (permalink / raw) To: gcc-bugs ------- Comment #2 from pinskia at gcc dot gnu dot org 2006-02-14 04:10 ------- What do you think it will do to 1000^2 expressions? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25647 ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug c++/25647] Large automaticallty generated code (unrolled loop) crashes the compiler 2006-01-03 8:01 [Bug c++/25647] New: Large automaticallty generated code (unrolled loop) crashes the compiler jonas dot mellin at his dot se 2006-01-03 8:03 ` [Bug c++/25647] " jonas dot mellin at his dot se 2006-02-14 4:10 ` pinskia at gcc dot gnu dot org @ 2006-03-08 5:14 ` bangerth at dealii dot org 2006-03-12 19:58 ` jonas dot mellin at his dot se 3 siblings, 0 replies; 5+ messages in thread From: bangerth at dealii dot org @ 2006-03-08 5:14 UTC (permalink / raw) To: gcc-bugs ------- Comment #3 from bangerth at dealii dot org 2006-03-08 05:14 ------- Your compiler simply runs out of memory. Don't do code like this. It will also not be very efficient. W. -- bangerth at dealii dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |WONTFIX http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25647 ^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug c++/25647] Large automaticallty generated code (unrolled loop) crashes the compiler 2006-01-03 8:01 [Bug c++/25647] New: Large automaticallty generated code (unrolled loop) crashes the compiler jonas dot mellin at his dot se ` (2 preceding siblings ...) 2006-03-08 5:14 ` bangerth at dealii dot org @ 2006-03-12 19:58 ` jonas dot mellin at his dot se 3 siblings, 0 replies; 5+ messages in thread From: jonas dot mellin at his dot se @ 2006-03-12 19:58 UTC (permalink / raw) To: gcc-bugs ------- 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 ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2006-03-12 19:58 UTC | newest] Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2006-01-03 8:01 [Bug c++/25647] New: Large automaticallty generated code (unrolled loop) crashes the compiler jonas dot mellin at his dot se 2006-01-03 8:03 ` [Bug c++/25647] " jonas dot mellin at his dot se 2006-02-14 4:10 ` pinskia at gcc dot gnu dot org 2006-03-08 5:14 ` bangerth at dealii dot org 2006-03-12 19:58 ` jonas dot mellin at his dot se
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).