public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/57615] New: power8 support does not deal with -mquad-memory -mno-vsx
@ 2013-06-14 19:14 meissner at gcc dot gnu.org
  2013-06-14 19:32 ` [Bug target/57615] " meissner at gcc dot gnu.org
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: meissner at gcc dot gnu.org @ 2013-06-14 19:14 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 57615
           Summary: power8 support does not deal with -mquad-memory
                    -mno-vsx
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: meissner at gcc dot gnu.org

Created attachment 30302
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30302&action=edit
Function to show the problem.

If you compile the Advance Toolchain dl-lookup.c with the following options:

-m64 dl-lookup.c -c -std=gnu99 -fgnu89-inline  -O3 -Wall -Winline
-Wwrite-strings -fmerge-all-constants -frounding-math -g -mcpu=power8
-mlong-double-128 -finline-limit=2000 -Wstrict-prototypes -mlong-double-128 
-fpic -fexceptions -fasynchronous-unwind-tables -ffixed-32 -ffixed-33
-ffixed-34 -ffixed-35 -ffixed-36 -ffixed-37 -ffixed-38 -ffixed-39 -ffixed-40
-ffixed-41 -ffixed-42 -ffixed-43 -ffixed-44 -ffixed-45 -ffixed-46 -ffixed-47
-ffixed-48 -ffixed-49 -ffixed-50 -ffixed-51 -ffixed-52 -ffixed-53 -ffixed-54
-ffixed-55 -ffixed-56 -ffixed-57 -ffixed-58 -ffixed-59 -ffixed-60 -ffixed-61
-ffixed-62 -ffixed-63 -ffixed-v0 -ffixed-v1 -ffixed-v10 -ffixed-v11 -ffixed-v12
-ffixed-v13 -ffixed-v14 -ffixed-v15 -ffixed-v16 -ffixed-v17 -ffixed-v18
-ffixed-v19 -ffixed-v2 -ffixed-v20 -ffixed-v21 -ffixed-v22 -ffixed-v23
-ffixed-v24 -ffixed-v25 -ffixed-v26 -ffixed-v27 -ffixed-v28 -ffixed-v29
-ffixed-v3 -ffixed-v30 -ffixed-v31 -ffixed-v4 -ffixed-v5 -ffixed-v6 -ffixed-v7
-ffixed-v8 -ffixed-v9 -ffixed-vrsave -ffixed-vscr -mno-altivec -mno-vsx

It fails with the message:
dl-lookup.c: In function ‘_dl_lookup_symbol_x’:
dl-lookup.c:854:1: error: could not split insn
(insn:TI 1693 4115 1696 (set (reg:TI 10 10 [orig:838 val2 ] [838])
        (mem/c:TI (reg/f:DI 18 18 [889]) [19 val2+0 S16 A128])) dl-lookup.c:976
454 {*movti_ppc64}
     (expr_list:REG_DEAD (reg/f:DI 18 18 [889])
        (expr_list:REG_EQUIV (mem/c:TI (reg/f:DI 22 22 [874]) [19 val+0 S16
A128])
            (nil))))
dl-lookup.c:854:1: internal compiler error: in final_scan_insn, at final.c:2887

This is due to the fact that I did not think about somebody having quad memory
enabled but not VSX instructions.  The non-VSX movti 64-bit insn always does a
"#" to split the insn, but the split function will not split it since it could
be handled by a "lq" instruction.

The fix is to use the function rs6000_output_move_128bit to properly generate
lq/stq if it is safe to do so.
>From gcc-bugs-return-424368-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jun 14 19:15:52 2013
Return-Path: <gcc-bugs-return-424368-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32580 invoked by alias); 14 Jun 2013 19:15:52 -0000
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
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 32538 invoked by uid 48); 14 Jun 2013 19:15:49 -0000
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/57615] power8 support does not deal with -mquad-memory -mno-vsx
Date: Fri, 14 Jun 2013 19:15: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-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: meissner at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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_status cf_reconfirmed_on cc assigned_to everconfirmed
Message-ID: <bug-57615-4-6ZRCCM8kto@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-57615-4@http.gcc.gnu.org/bugzilla/>
References: <bug-57615-4@http.gcc.gnu.org/bugzilla/>
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: 2013-06/txt/msg00747.txt.bz2
Content-length: 645

http://gcc.gnu.org/bugzilla/show_bug.cgi?idW615

Michael Meissner <meissner at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2013-06-14
                 CC|                            |bergner at gcc dot gnu.org,
                   |                            |dje.gcc at gmail dot com
           Assignee|unassigned at gcc dot gnu.org      |meissner at gcc dot gnu.org
     Ever confirmed|0                           |1


^ permalink raw reply	[flat|nested] 4+ messages in thread
end of thread, other threads:[~2014-04-04 13:40 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-06-14 19:14 [Bug target/57615] New: power8 support does not deal with -mquad-memory -mno-vsx meissner at gcc dot gnu.org
2013-06-14 19:32 ` [Bug target/57615] " meissner at gcc dot gnu.org
2013-06-14 20:55 ` meissner at gcc dot gnu.org
2014-04-04 13:40 ` wschmidt at gcc dot gnu.org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).