From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12381 invoked by alias); 13 Nov 2004 17:52:22 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 12368 invoked by uid 48); 13 Nov 2004 17:52:20 -0000 Date: Sat, 13 Nov 2004 17:52:00 -0000 Message-ID: <20041113175220.12367.qmail@sourceware.org> From: "steven at gcc dot gnu dot org" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20041113170938.18463.steven@gcc.gnu.org> References: <20041113170938.18463.steven@gcc.gnu.org> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug tree-optimization/18463] [4.0 Regression] Moving floating point through an integer register X-Bugzilla-Reason: CC X-SW-Source: 2004-11/txt/msg01659.txt.bz2 List-Id: ------- Additional Comments From steven at gcc dot gnu dot org 2004-11-13 17:52 ------- At least x86 and ARM have {reg + reg OP const} addressing modes. Unfortunately we rip such expressions apart already in the gimplifier. This is something we canot fix properly on trees. TER could perhaps do it, but that pass should really go away itself, and we don't know anything about addressing modes on trees anyway. Looks like we need to teach an RTL loop optimizer about this... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18463