From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22902 invoked by alias); 14 Apr 2009 14:43:44 -0000 Received: (qmail 22887 invoked by uid 22791); 14 Apr 2009 14:43:43 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.33.17) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 14 Apr 2009 14:43:38 +0000 Received: from zps78.corp.google.com (zps78.corp.google.com [172.25.146.78]) by smtp-out.google.com with ESMTP id n3EEhYCL004785; Tue, 14 Apr 2009 15:43:35 +0100 Received: from smtp.corp.google.com (spacemonkey1.corp.google.com [192.168.120.115]) by zps78.corp.google.com with ESMTP id n3EEhWYc019179 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 14 Apr 2009 07:43:33 -0700 Received: from localhost.localdomain.google.com (67-218-102-28.cust.layer42.net [67.218.102.28] (may be forged)) (authenticated bits=0) by smtp.corp.google.com (8.13.8/8.13.8) with ESMTP id n3EEhRhg000870 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 14 Apr 2009 07:43:31 -0700 To: Georg-Johann Lay Cc: gcc-help@gcc.gnu.org Subject: Re: Reload pass ignores constraints. Why? References: <49E4673B.10903@gjlay.de> From: Ian Lance Taylor Date: Tue, 14 Apr 2009 14:43:00 -0000 In-Reply-To: <49E4673B.10903@gjlay.de> (Georg-Johann Lay's message of "Tue\, 14 Apr 2009 12\:36\:43 +0200") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-System-Of-Record: true X-IsSubscribed: yes 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 X-SW-Source: 2009-04/txt/msg00141.txt.bz2 Georg-Johann Lay writes: > Working out recommendations for a new instruction set architecture (no > silicon yet), I run into the following problem with a port based on > gcc_4_3_3_release: postreload complains >From your description, I would have expected reload to handle this correctly. I don't know why it didn't. The first place to look would be to verify that the REG_CLASS_CONTENTS bitmasks are correct. Next, look at the .greg dump to see if the insn in question required any reloads. If not, the next step may be to debug find_reloads to find out why no reloads were required. This can somewhat tedious; you can set a breakpoint to match the insn UID so that you are looking at the right insn in find_reloads, but following the loops can still take a while. Good luck. I've spent many days on this sort of problem. Ian