public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sgunderson at bigfoot dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/57623] New: BEXTR intrinsic has memory operands switched around (fails to compile code) Date: Sat, 15 Jun 2013 14:29:00 -0000 [thread overview] Message-ID: <bug-57623-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57623 Bug ID: 57623 Summary: BEXTR intrinsic has memory operands switched around (fails to compile code) Product: gcc Version: 4.8.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: sgunderson at bigfoot dot com Hi, Given I'm on gcc 4.8.1 (Debian 4.8.1-2). Given the following test program: sesse@gruessi:~$ cat bextr-test.c #include <stdint.h> uint64_t func(uint64_t x, uint64_t *y) { return __builtin_ia32_bextr_u64(x, *y); } trying to compile it fails: sesse@gruessi:~$ gcc-4.8 -O2 -mbmi -c bextr-test.c --save-temps bextr-test.s: Assembler messages: bextr-test.s:9: Error: operand size mismatch for `bextr' seemingly because GCC's idea of r/m is broken for this instruction: sesse@gruessi:~$ cat bextr-test.s .file "bextr-test.c" .text .p2align 4,,15 .globl func .type func, @function func: .LFB0: .cfi_startproc bextr (%rsi), %rdi, %rax ret .cfi_endproc .LFE0: .size func, .-func .ident "GCC: (Debian 4.8.1-2) 4.8.1" .section .note.GNU-stack,"",@progbits As far as I understand, the second operand can be r/m64, but the first can only be r64.
next reply other threads:[~2013-06-15 14:29 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-06-15 14:29 sgunderson at bigfoot dot com [this message] 2013-06-15 16:33 ` [Bug target/57623] " jakub at gcc dot gnu.org 2013-06-15 17:01 ` sgunderson at bigfoot dot com 2013-06-15 17:13 ` sgunderson at bigfoot dot com 2013-06-17 7:56 ` jakub at gcc dot gnu.org 2013-06-27 11:19 ` sgunderson at bigfoot dot com 2013-06-27 12:13 ` jakub at gcc dot gnu.org 2013-06-27 12:25 ` sgunderson at bigfoot dot com 2013-06-27 12:27 ` jakub at gcc dot gnu.org 2013-06-27 12:42 ` sgunderson at bigfoot dot com 2013-06-27 12:43 ` sgunderson at bigfoot dot com 2013-06-27 12:49 ` jakub at gcc dot gnu.org 2013-06-27 16:50 ` jakub at gcc dot gnu.org 2014-05-07 15:55 ` jakub at gcc dot gnu.org 2014-05-07 15:58 ` jakub at gcc dot gnu.org 2014-05-07 16:17 ` 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-57623-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: linkBe 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).