On Sun, Aug 17, 2014 at 6:48 PM, Chen Gang <gang.chen.5...@gmail.com> wrote: > On 08/10/2014 04:15 PM, Chen Gang wrote: >> On 08/10/2014 04:03 PM, Mike Stump wrote: >>> On Aug 9, 2014, at 9:55 AM, Chen Gang <gang.chen.5...@gmail.com> wrote: >>>>> <save various .sum files> >>>> >>>> Excuse me, I can not find it with `find ./ | grep "\.sum$"` >>> >>> Then you didn't do a test suite run. make check will create .sum files. >>> Try cd gcc && make check. Then in testsuite/gcc/gcc.sum there will be a >>> file. >>> > > After check again, I found, I did not install runtest (but it skipped, > and let "make check" OK), after install from 'dejagnu', can have real > effect. At present (just running "make check"), some results are: > > Running > /upstream/toolchain/gcc/gcc/testsuite/gcc.c-torture/compile/compile.exp ... > FAIL: gcc.c-torture/compile/20001226-1.c -O0 (internal compiler error) > FAIL: gcc.c-torture/compile/20001226-1.c -O0 (test for excess errors) > FAIL: gcc.c-torture/compile/20001226-1.c -O3 -g (internal compiler error) > FAIL: gcc.c-torture/compile/20001226-1.c -O3 -g (test for excess errors) > FAIL: gcc.c-torture/compile/limits-blockid.c -O0 (internal compiler > error) > FAIL: gcc.c-torture/compile/limits-blockid.c -O0 (test for excess errors) > FAIL: gcc.c-torture/compile/limits-caselabels.c -O1 (internal compiler > error) > FAIL: gcc.c-torture/compile/limits-caselabels.c -O1 (test for excess > errors) > FAIL: gcc.c-torture/compile/limits-enumconst.c -O0 (internal compiler > error) > FAIL: gcc.c-torture/compile/limits-enumconst.c -O0 (test for excess > errors) > FAIL: gcc.c-torture/compile/limits-enumconst.c -O1 (internal compiler > error) > FAIL: gcc.c-torture/compile/limits-enumconst.c -O1 (test for excess > errors) > FAIL: gcc.c-torture/compile/limits-enumconst.c -O3 -g (internal compiler > error) > FAIL: gcc.c-torture/compile/limits-enumconst.c -O3 -g (test for excess > errors) > FAIL: gcc.c-torture/compile/limits-enumconst.c -O2 -flto > -fuse-linker-plugin -fno-fat-lto-objects (internal compiler error) > FAIL: gcc.c-torture/compile/limits-enumconst.c -O2 -flto > -fuse-linker-plugin -fno-fat-lto-objects (test for excess errors) > FAIL: gcc.c-torture/compile/limits-externalid.c -O3 -g (internal > compiler error) > FAIL: gcc.c-torture/compile/limits-externalid.c -O3 -g (test for excess > errors) > FAIL: gcc.c-torture/compile/limits-externalid.c -Os (internal compiler > error) > FAIL: gcc.c-torture/compile/limits-externalid.c -Os (test for excess > errors) > FAIL: gcc.c-torture/compile/limits-externdecl.c -O2 (test for excess > errors) Hi, You can run below command for a single failed case, which makes it easier to identify the problem. $ make check-gcc RUNTESTFLAGS="compile.exp=20001226-1.c" Then you could look into file gcc/testsuite/gcc/gcc.log for stack back-trace of internal compiler error. Usually ICE is easy to reslove, most likely your change overlooks some simple cases.
Thanks, bin > ... > > Do these contents mean: I make any incorrect configuration, again? > > >> >> OK, thanks, I built it under individual directory "build-gcc", I guess >> your meaning is "cd ./build-gcc/gcc && make check". If what I guess is >> incorrect, please let me know, thanks. >> >>>> After comparing, should the related ".sum" files be the same (same means >>>> pass checking)? >>> >>> No, use contrib/compare_tests before_dir after_dir :-) If you _save_off >>> the .sum files, you can use the places where you same them off. If you use >>> two trees, you can just use them directly (no saving off). >>> >>> where the two are the build directories that you did a make check in. The >>> output will be in simple english and should be readily understandable. >>> > > After try, I found your information about 2 build directories are very > useful for me, which can same much time under smp machine. > > And sorry, I did not finish "make check" at the time point. I wasted my > time resources (of my free time) on constructing PC environments and my > x86_64 laptop environments. > > - x86_64 laptop under ubuntu: try to update 'libc6' package to install > 'autogen'. At last, I succeed: overwrite libc6 package files under > individual living system, and then modify dpkg config file manually. > > - PC environments: I failed, the reason is my PC hardware is not stable > enough (low quality). After building several hours, the machine will > reboot automatically (tried several times, each needs several hours). > > And I shall try to finish as soon as possible (may tomorrow or the day > after tomorrow, under Mac book, and within a week under x86_64 laptop). > >> >> OK, Thanks, and I shall try to finish within next week (one building is >> still very long, although I have switched to mac book -- more higher >> performance machine). >> >> >> Thanks. >> > > Thanks. > -- > Chen Gang > > Open, share, and attitude like air, water, and life which God blessed
