[Bug tree-optimization/34147] internal compiler error: in set_iv, at tree-ssa-loop-ivopts.c:936
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=34147 Marek Polacek mpolacek at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mpolacek at gcc dot gnu.org Resolution|--- |INVALID --- Comment #12 from Marek Polacek mpolacek at gcc dot gnu.org --- Let's close this one.
[Bug tree-optimization/34147] internal compiler error: in set_iv, at tree-ssa-loop-ivopts.c:936
--- Comment #8 from huamama at gmail dot com 2007-11-21 10:24 --- Thanks. The complie flag in the Makefile of Busybox is /opt/arm/bin/arm-linux-gcc -I/home/mahua/opt/test/busybox-1.1.3/include -I/home/mahua/opt/test/busybox-1.1.3/include -I/home/mahua/opt/test/busybox-1.1.3/libbb -funsigned-char -Wall -Wstrict-prototypes -Wshadow -Os -funit-at-a-time -fstrict-aliasing -fomit-frame-pointer -D_GNU_SOURCE -DNDEBUG -Wl,--warn-common -Wl,--sort-common -Wl,--start-group -Wl,--end-group, I guess it is also the compile flag for file editor/vi.c. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34147
[Bug tree-optimization/34147] internal compiler error: in set_iv, at tree-ssa-loop-ivopts.c:936
--- Comment #9 from ubizjak at gmail dot com 2007-11-21 11:15 --- (In reply to comment #8) Thanks. The complie flag in the Makefile of Busybox is /opt/arm/bin/arm-linux-gcc -I/home/mahua/opt/test/busybox-1.1.3/include -I/home/mahua/opt/test/busybox-1.1.3/include -I/home/mahua/opt/test/busybox-1.1.3/libbb -funsigned-char -Wall -Wstrict-prototypes -Wshadow -Os -funit-at-a-time -fstrict-aliasing -fomit-frame-pointer -D_GNU_SOURCE -DNDEBUG -Wl,--warn-common -Wl,--sort-common -Wl,--start-group -Wl,--end-group, I guess it is also the compile flag for file editor/vi.c. Hm, the testcase compiles OK for me using '~/arm-gcc-4.1/gcc/cc1 -funsigned-char -Os -funit-at-a-time -fstrict-aliasing pr34147.i' and gcc version 4.1.3 20070620 (prerelease), Target: arm-elf So the bug is not triggered by these flags. Perhaps the bug is already fixed in current SVN branch. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34147
[Bug tree-optimization/34147] internal compiler error: in set_iv, at tree-ssa-loop-ivopts.c:936
--- Comment #10 from huamama at gmail dot com 2007-11-22 01:38 --- hi, I also build the toolchains in linux, and when compile busybox using the same configuration, no compile error will shown. And only when i build the toolchains in cygwin, when compile the busybox using the same configuration, error will shown. aslo, in cygwin, if CONFIG_BUILD_AT_ONCE=y is not selected, when compile vi.c , no error will shown, but if CONFIG_BUILD_AT_ONCE=y is selected, when compile vi.c, error will shown. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34147
[Bug tree-optimization/34147] internal compiler error: in set_iv, at tree-ssa-loop-ivopts.c:936
--- Comment #11 from huamama at gmail dot com 2007-11-22 01:51 --- Below is the CONFIG_BUILD_AT_ONCE in busybox is detailed in configuration file of buysbox, Does that mean in cygwin, maybe the ram is less than 300M, so when compile all the busybox, some unexpected internal compiler error will shown. I think the vi.c is ok with compile, because if i select only vi and some other fewer package in busybox configuration, the compile is also fine, but if more packages are selected, an error will shown, sometime is segmentation fault in vi.c, sometime is internal compiler error: in set_iv, at tree-ssa-loop-ivopts.c:. Is that something wrong if compile many things using gcc an error will shown? Thanks. config CONFIG_BUILD_AT_ONCE bool Compile all sources at once default n help Normally each source-file is compiled with one invocation of the compiler. If you set this option, all sources are compiled at once. This gives the compiler more opportunities to optimize which can result in smaller and/or faster binaries. Setting this option will consume alot of memory, e.g. if you enable all applets with all features, gcc uses more than 300MB RAM during compilation of busybox. This option is most likely only beneficial for newer compilers such as gcc-4.1 and above. Say 'N' unless you know what you are doing. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34147
[Bug tree-optimization/34147] internal compiler error: in set_iv, at tree-ssa-loop-ivopts.c:936
--- Comment #3 from ubizjak at gmail dot com 2007-11-20 08:01 --- (In reply to comment #2) I build the toolchains use buildroot, the gcc version is 4.1.2, the target platform is arm, host platform is cygwin. The busybox version is 1.1.3 If i uncomment some configure of busybox, a new error will show as following: Go into directory /home/mahua/opt/test/busybox-1.1.3/editors/ and type: prefixgcc compile-flags -save-temps vi.c, where prefix is something like arm-elf- or arm-linux-elf- and compile-flags is complete compile flags, copied from the compile log, since these usually span several lines. Please post _complete_ command how gcc was invoked (so we can use your compile flags) and attach generated vi.i from /home/mahua/opt/test/busybox-1.1.3/editors/ to this report. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34147
[Bug tree-optimization/34147] internal compiler error: in set_iv, at tree-ssa-loop-ivopts.c:936
--- Comment #4 from huamama at gmail dot com 2007-11-21 02:01 --- Created an attachment (id=14586) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14586action=view) the temp vi.c using -save-temps file the temp vi.c using -save-temps file when compile busybox using CONFIG_BUILD_AT_ONCE=y. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34147
[Bug tree-optimization/34147] internal compiler error: in set_iv, at tree-ssa-loop-ivopts.c:936
--- Comment #5 from huamama at gmail dot com 2007-11-21 02:02 --- I found when i compile busybox using CONFIG_BUILD_AT_ONCE=y, the error will happen, but if do not use CONFIG_BUILD_AT_ONCE=y, the compile will success. The temp file using -save-temps is attached with CONFIG_BUILD_AT_ONCE=y. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34147
[Bug tree-optimization/34147] internal compiler error: in set_iv, at tree-ssa-loop-ivopts.c:936
--- Comment #6 from huamama at gmail dot com 2007-11-21 02:08 --- Created an attachment (id=14587) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14587action=view) the temp vi.c using -save-temps file, using 4.1.2 the temp vi.c using -save-temps file -- huamama at gmail dot com changed: What|Removed |Added Attachment #14586|0 |1 is obsolete|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34147
[Bug tree-optimization/34147] internal compiler error: in set_iv, at tree-ssa-loop-ivopts.c:936
--- Comment #7 from ubizjak at gmail dot com 2007-11-21 07:34 --- (In reply to comment #6) the temp vi.c using -save-temps file Thanks, but we also need flags that were passed to gcc when editors/vi.c was compiled. Probably you have to enable verbose output from your compile scripts. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34147
[Bug tree-optimization/34147] internal compiler error: in set_iv, at tree-ssa-loop-ivopts.c:936
--- Comment #2 from huamama at gmail dot com 2007-11-20 03:30 --- I build the toolchains use buildroot, the gcc version is 4.1.2, the target platform is arm, host platform is cygwin. The busybox version is 1.1.3 If i uncomment some configure of busybox, a new error will show as following: LINK busybox_unstripped /home/mahua/opt/test/busybox-1.1.3/networking/telnetd.c: In function 'telnetd_main': /home/mahua/opt/test/busybox-1.1.3/networking/telnetd.c:541: warning: pointer targets in passing argument 3 of 'accept' differ in signedness /home/mahua/opt/test/busybox-1.1.3/editors/vi.c: In function 'do_cmd': /home/mahua/opt/test/busybox-1.1.3/editors/vi.c:3846: 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. make[1]: *** [busybox_unstripped] Error 1 make: *** [_all] Error 2 -- huamama at gmail dot com changed: What|Removed |Added CC||huamama at gmail dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34147
[Bug tree-optimization/34147] internal compiler error: in set_iv, at tree-ssa-loop-ivopts.c:936
--- Comment #1 from ubizjak at gmail dot com 2007-11-19 07:17 --- Please provide a testcase, as outlined in http://gcc.gnu.org/bugs.html. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34147
