public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamrial at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65671] New: Assembly failure (invalid register operand) with -O3 -mavx512vl
Date: Sat, 04 Apr 2015 04:57:00 -0000	[thread overview]
Message-ID: <bug-65671-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65671

            Bug ID: 65671
           Summary: Assembly failure (invalid register operand) with -O3
                    -mavx512vl
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jamrial at gmail dot com

https://raw.githubusercontent.com/foo86/dcadec/e884d9a0d9127528bdc47c1f8db392363fb50876/libdcadec/idct_float.c

gcc -O3 -mavx512f -mavx512vl -c -o libdcadec/idct_float.o
libdcadec/idct_float.c
/tmp/cc3BQBvH.s: Assembler messages:
/tmp/cc3BQBvH.s:1602: Error: invalid register operand for `vextractf128'
/tmp/cc3BQBvH.s:1624: Error: invalid register operand for `vextractf128'
/tmp/cc3BQBvH.s:1670: Error: invalid register operand for `vextractf128'

Lines in question from the resulting assembly file

1602: vextractf128    $0x1, %ymm20, 144(%rdx)
1624: vextractf128    $0x1, %ymm24, 272(%rdx)
1670: vextractf128    $0x1, %ymm19, 400(%rdx)

GCC 5.0.0 (20150329 snapshot) on x86_64-unknown-linux-gnu. Works fine with
-mavx512f alone, so sounds like the assembler is trying to use VEX coding
scheme with the new registers instead of EVEX.


             reply	other threads:[~2015-04-04  4:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-04  4:57 jamrial at gmail dot com [this message]
2015-04-08 11:06 ` [Bug target/65671] " kyukhin at gcc dot gnu.org
2015-04-09  9:45 ` kyukhin at gcc dot gnu.org
2015-04-09 21:38 ` kyukhin at gcc dot gnu.org
2015-04-09 21:39 ` kyukhin at gcc dot gnu.org
2015-04-11 13:57 ` jakub at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-65671-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).