From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26119 invoked by alias); 22 Feb 2012 19:29:48 -0000 Received: (qmail 26090 invoked by uid 22791); 22 Feb 2012 19:29:46 -0000 X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,TW_SV X-Spam-Check-By: sourceware.org Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 22 Feb 2012 19:29:24 +0000 Received: from nat-dem.mentorg.com ([195.212.93.2] helo=eu2-mail.mgc.mentorg.com) by relay1.mentorg.com with esmtp id 1S0HsQ-0001SQ-Lj from Thomas_Schwinge@mentor.com ; Wed, 22 Feb 2012 11:29:22 -0800 Received: from feldtkeller.schwinge.homeip.net ([172.30.64.116]) by eu2-mail.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 22 Feb 2012 20:29:21 +0100 From: Thomas Schwinge To: Kaz Kojima , gcc@gcc.gnu.org Cc: Kevin Buettner , gdb-patches@sourceware.org Subject: Re: Simulator testing for sh and sh64 In-Reply-To: <20120222093929.7e86fba2@mesquite.lan> References: <87pqdgciho.fsf@schwinge.name> <20120215075413.1313f7fa@mesquite.lan> <20120215165907.33f2e9a6@mesquite.lan> <8739aad9il.fsf@schwinge.name> <20120216182544.36b41a1b@mesquite.lan> <87zkca9azw.fsf@schwinge.name> <20120222093929.7e86fba2@mesquite.lan> User-Agent: Notmuch/0.9-101-g81dad07 (http://notmuchmail.org) Emacs/23.3.1 (x86_64-pc-linux-gnu) Date: Wed, 22 Feb 2012 19:33:00 -0000 Message-ID: <87wr7e8y60.fsf@schwinge.name> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-02/txt/msg00483.txt.bz2 --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-length: 4347 Hi! This is about sh and sh64 GDB sim testing for the whole toolchain. (I also do have sh4a hardware available, where testing is working fine.) Kaz, could you please have a look whether this looks basically sane, that my assumptions and the results I'm getting are about right, etc.? On Wed, 22 Feb 2012 09:39:29 -0700, Kevin Buettner wrot= e: > On Wed, 22 Feb 2012 15:52:03 +0100 > Thomas Schwinge wrote: >=20 > > How do you configure the toolchain's components for the sim testing? >=20 > I use --target=3Dsh-elf . >=20 > When it comes time to run the tests, do: >=20 > make check RUNTESTFLAGS=3D"--target_board=3Dsh-sim" OK, that matches what I'm doing (simple enough), and that works for me, too. With all-current sources (CVS HEAD, svn trunk, Git master, as appropriate), I get 707 unexpected failures in g++ testing (a lot of execution tests, as it seems), 204 in gcc, 434 in gdb (I'm currently working on improving that), 41 in ld (seems that some test harness problem is involved; get a lot of: ``sh-elf-ld: cannot find sh-unknown.o: No such file or directory''), 322 in libstdc++, 3 in newlib. So far, so good. > > And, any quick suggestion for a sh64 sim testing configuration, too? My > > attempt so far only results in a series of SIGILL... Kaz, is my understanding correct, that I simply use sh64-elf as target, and again the sh-sim board? Should I be setting a specific CPU when configuring GCC, or any other customization? Building all-current sources comes to a halt as follows: /scratch/tschwing/FM_sh64-elf/obj/gcc-first-mainline-0-sh64-elf-i686-pc= -linux-gnu/./gcc/xgcc -B/scratch/tschwing/FM_sh64-elf/obj/gcc-first-mainlin= e-0-sh64-elf-i686-pc-linux-gnu/./gcc/ -B/scratch/tschwing/FM_sh64-elf/insta= ll/sh64-elf/bin/ -B/scratch/tschwing/FM_sh64-elf/install/sh64-elf/lib/ -isy= stem /scratch/tschwing/FM_sh64-elf/install/sh64-elf/include -isystem /scrat= ch/tschwing/FM_sh64-elf/install/sh64-elf/sys-include --sysroot=3D/scratch/t= schwing/FM_sh64-elf/install/sh64-elf -g -O2 -ml -O2 -g -O2 -DIN_GCC -DCR= OSS_DIRECTORY_STRUCTURE -W -Wall -Wwrite-strings -Wcast-qual -Wstrict-prot= otypes -Wmissing-prototypes -Wold-style-definition -isystem ./include -m= ieee -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector -Dinhibit_libc = -mieee -I. -I. -I../../.././gcc -I/scratch/tschwing/FM_sh64-elf/src/gcc-ma= inline/libgcc -I/scratch/tschwing/FM_sh64-elf/src/gcc-mainline/libgcc/. -I/= scratch/tschwing/FM_sh64-elf/src/gcc-mainline/libgcc/../gcc -I/scratch/tsch= wing/FM_sh64-elf/src/gcc-mainline/libgcc/../include -DHAVE_CC_TLS -DUSE_EM= UTLS -o _powisf2.o -MT _powisf2.o -MD -MP -MF _powisf2.dep -DL_powisf2 -c /= scratch/tschwing/FM_sh64-elf/src/gcc-mainline/libgcc/libgcc2.c=20 /scratch/tschwing/FM_sh64-elf/src/gcc-mainline/libgcc/libgcc2.c: In fun= ction '__powisf2': /scratch/tschwing/FM_sh64-elf/src/gcc-mainline/libgcc/libgcc2.c:1779:1:= error: unrecognizable insn: (insn 10 9 11 3 (set (reg:SI 162 [ D.2769 ]) (abs:SI (reg/v:SI 168 [ m ]))) /scratch/tschwing/FM_sh64-elf/sr= c/gcc-mainline/libgcc/libgcc2.c:1770 -1 (nil)) /scratch/tschwing/FM_sh64-elf/src/gcc-mainline/libgcc/libgcc2.c:1779:1:= internal compiler error: in extract_insn, at recog.c:2123 Stepping back to using the 4.5 GCC branch and otherwise all-current sources, it compiles, and I get 76 unexpected failures in g++ (a lot of ``ld: section .stack loaded at [0000000000080000,0000000000080003] overlaps section .text loaded at [0000000000001060,00000000000ec0bf]''), 119 in gcc, 41 in ld, 1185 in libstdc++ (the section overlap issue again, it seems), 3 in newlib, and GDB testing totally breaks down: I'm receiving a lot of ``Program received signal SIGILL, Illegal instruction''; from a quick investigation, it seems that GDB is patching the breakpoints at addresses that are 2 bytes offset from where they meant to go. I'll have a look at this. Moving a bit forward by using the 4.6 GCC branch and otherwise all-current sources, it compiles, and the test results look similar to GCC 4.5's. This means, for sh-elf sim testing, we have a bit too many failures in GCC and GDB, and some ld test harness issue. For sh64-elf we have a GCC trunk ICE, some section overlap issue, and even more GDB issues. Gr=C3=BC=C3=9Fe, Thomas --=-=-= Content-Type: application/pgp-signature Content-length: 489 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAEBAgAGBQJPRUIHAAoJENuKOtuXzphJ5lcH/ReOHAX6MvTjbm2NbJ1OV9xm XATk9oEiFZT4bssaRgtTvfUGMH0yCbbWrTWCUA91mUouE/lzSAmIfftarivrZSk6 PpRuxzzmYmjfYN41Es1B2JDDzFhD4MPIkXUABkY8F+Kib3Vp/TTZXobBFI90kcT5 HFfPhAcMtuHhO4B4TMvlQJ9Y88zHLG9foLT0GCM2w/veKzMXIH52uBLa5utYA4qD SFZxGpWhohYf8vpq/ZYuvCR2hIQTUyiMRpZmXzP+32eu0GmhjLyULiHZgx1tBfwD sd6YBWBPTWc0Ycolyr+zYK6SIosRQpTIhkXqYDnJ1yiVZfE/aATUamvzwNP+77E= =dlOY -----END PGP SIGNATURE----- --=-=-=--