From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31383 invoked by alias); 20 Aug 2011 07:44:20 -0000 Received: (qmail 31375 invoked by uid 22791); 20 Aug 2011 07:44:19 -0000 X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-yi0-f47.google.com (HELO mail-yi0-f47.google.com) (209.85.218.47) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 20 Aug 2011 07:43:58 +0000 Received: by yia28 with SMTP id 28so2761627yia.20 for ; Sat, 20 Aug 2011 00:43:58 -0700 (PDT) Received: by 10.236.116.233 with SMTP id g69mr1394509yhh.39.1313826238070; Sat, 20 Aug 2011 00:43:58 -0700 (PDT) Received: from pauldell (124-149-34-246.dyn.iinet.net.au [124.149.34.246]) by mx.google.com with ESMTPS id c63sm873181yhe.60.2011.08.20.00.43.54 (version=SSLv3 cipher=OTHER); Sat, 20 Aug 2011 00:43:56 -0700 (PDT) Message-ID: From: "Paul Edwards" To: "Ulrich Weigand" Cc: Subject: Re: i370 port Date: Sat, 20 Aug 2011 07:44:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2011-08/txt/msg00362.txt.bz2 > (like the 8 byte move from F'0'). I'll do my own investigation > of that and report that later. Ok, the bad MVC: MVC 112(8,13),=F'0' is being generated by the movdi instruction: ; ; movdi instruction pattern(s). ; (define_insn "" [(set (match_operand:DI 0 "nonimmediate_operand" "=d,m,S") (match_operand:DI 1 "general_operand" "g,d,SF"))] ;; [(set (match_operand:DI 0 "r_or_s_operand" "=dS,m") ;; (match_operand:DI 1 "r_or_s_operand" "diS*fF,d*fF"))] "TARGET_CHAR_INSTRUCTIONS" "* { ... return \"MVC^I%O0(8,%R0),%1\"; }" which looks correct to me. The problem seems to be an =F'0' being treated as a DI operand. That extra memory constraint thing must be allowing this rogue value through that was normally not picked up. Any ideas? Thanks. Paul.