From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29740 invoked by alias); 5 Jan 2015 21:04:47 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 29709 invoked by uid 48); 5 Jan 2015 21:04:43 -0000 From: "meissner at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/64505] New: Powerpc compiler generates insn not found for -m32 -mpowerpc64 Date: Mon, 05 Jan 2015 21:04:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: meissner at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: meissner at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cf_gcchost cf_gcctarget cf_gccbuild attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-01/txt/msg00269.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64505 Bug ID: 64505 Summary: Powerpc compiler generates insn not found for -m32 -mpowerpc64 Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: meissner at gcc dot gnu.org Reporter: meissner at gcc dot gnu.org Host: powerpc64-unknown-linux-gnu Target: powerpc64-unknown-linux-gnu Build: powerpc64-unknown-linux-gnu Created attachment 34384 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34384&action=edit File that shows the problem Compiling the attached file will generate an insn not found error message if it is compiled with the following options: -std=c99 -fno-strict-aliasing -Wall -m32 -mpowerpc64 foo.c -S -O2. The problem is inside of rs6000_secondary_reload, there is code for 64-bit and 32-bit. The reload insn that is returned is looking for a 64-bit scratch register, but the combination of switches -m32 -mpowerpc64 it should be generating a 32-bit scratch register.