From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21172 invoked by alias); 30 Jan 2015 23:01:44 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 21136 invoked by uid 89); 30 Jan 2015 23:01:43 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: resqmta-po-05v.sys.comcast.net Received: from resqmta-po-05v.sys.comcast.net (HELO resqmta-po-05v.sys.comcast.net) (96.114.154.164) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Fri, 30 Jan 2015 23:01:42 +0000 Received: from resomta-po-12v.sys.comcast.net ([96.114.154.236]) by resqmta-po-05v.sys.comcast.net with comcast id mP1N1p00256HXL001P1fXE; Fri, 30 Jan 2015 23:01:39 +0000 Received: from [IPv6:2001:558:6045:a4:40c6:7199:cd03:b02d] ([IPv6:2001:558:6045:a4:40c6:7199:cd03:b02d]) by resomta-po-12v.sys.comcast.net with comcast id mP1b1p00V2ztT3H01P1cPv; Fri, 30 Jan 2015 23:01:37 +0000 Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: [Consult] tile: How to construct testsuite for tile architecture without hardware. From: Mike Stump In-Reply-To: <54CC0C79.1070007@sunrus.com.cn> Date: Fri, 30 Jan 2015 23:01:00 -0000 Cc: Chris Metcalf , walt@tilera.com, Jeff Law , gcc-help , Michael Eager Content-Transfer-Encoding: quoted-printable Message-Id: References: <54BA30F3.4080202@sunrus.com.cn> <54BD2C5E.1070804@ezchip.com> <54BDB71D.90703@sunrus.com.cn> <54C39ECA.3000603@sunrus.com.cn> <54CC0C79.1070007@sunrus.com.cn> To: Chen Gang S X-SW-Source: 2015-01/txt/msg00170.txt.bz2 On Jan 30, 2015, at 2:58 PM, Chen Gang S wrote: > After finish analyzing the related warnings for tile, for me, they are > neither tile's issues nor gcc common implementation issues: ? They all look like they can be fixed in the port. Why not use :P? From i386: ;; This mode iterator allows :P to be used for patterns that operate on=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 ;; pointer-sized quantities. Exactly one of the two alternatives will matc= h.=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 (define_mode_iterator P [(SI "Pmode =3D=3D SImode") (DI "Pmode =3D=3D DImod= e")]) (define_insn "*tls_global_dynamic_64_" [(set (match_operand:P 0 "register_operand" "=3Da") (call:P (mem:QI (match_operand 2 "constant_call_address_operand" "Bz")) (match_operand 3))) (unspec:P [(match_operand 1 "tls_symbolic_operand")] UNSPEC_TLS_GD)] =93TARGET_64BIT" > ../../gcc-tile-new/gcc/config/tilegx/tilegx.md:2627: warning: operand 0 m= issing mode? > ../../gcc-tile-new/gcc/config/tilegx/tilegx.md:2656: warning: operand 0 = missing mode? > ../../gcc-tile-new/gcc/config/tilegx/tilegx.md:2890: warning: operand 1 = missing mode? > ../../gcc-tile-new/gcc/config/tilegx/tilegx.md:2890: warning: operand 1 = missing mode? > ../../gcc-tile-new/gcc/config/tilegx/tilegx.md:2986: warning: operand 3 = missing mode? > ../../gcc-tile-new/gcc/config/tilegx/tilegx.md:3030: warning: operand 1 = missing mode? > ../../gcc-tile-new/gcc/config/tilegx/tilegx.md:3030: warning: operand 1 = missing mode? > ../../gcc-tile-new/gcc/config/tilegx/tilegx.md:3115: warning: operand 1 = missing mode? > ../../gcc-tile-new/gcc/config/tilegx/tilegx.md:3115: warning: operand 1 = missing mode? > ../../gcc-tile-new/gcc/config/tilegx/tilegx.md:3127: warning: operand 1 = missing mode? > ../../gcc-tile-new/gcc/config/tilegx/tilegx.md:3127: warning: operand 1 = missing mode? > ../../gcc-tile-new/gcc/config/tilegx/tilegx.md:3140: warning: operand 1 = missing mode? > ../../gcc-tile-new/gcc/config/tilegx/tilegx.md:3140: warning: operand 1 = missing mode?