From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-405288-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 11595 invoked by alias); 31 Oct 2012 15:48:31 -0000
Received: (qmail 9705 invoked by uid 48); 31 Oct 2012 15:47:50 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/55147] x86: wrong code for 64-bit load
Date: Wed, 31 Oct 2012 15:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields:
Message-ID: <bug-55147-4-Uk2GQ4jEyP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55147-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55147-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2012-10/txt/msg02964.txt.bz2


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55147

--- Comment #2 from Uros Bizjak <ubizjak at gmail dot com> 2012-10-31 15:47:46 UTC ---
> can fix the reg overlap problem between address of operands[1] and high part of
> operands[0].  That said, I wonder what is the advantage of having bswapdi2
> patter on i?86 at all that the generic expand_doubleword_bswap can't handle.

If generic code creates similar assembly, then I'm all for removing this
pattern.