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] BEXTR intrinsic has memory operands switched around (fails to compile code)
Date: Sat, 15 Jun 2013 17:01:00 -0000	[thread overview]
Message-ID: <bug-57623-4-GwtB3Lj1Kl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57623-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from sgunderson at bigfoot dot com ---
On Sat, Jun 15, 2013 at 04:33:14PM +0000, jakub at gcc dot gnu.org wrote:
> The fix for the compiler is easy, but at least the AVX2 spec documents that
> _bextr_u{32,64} intrinsics actually take 3 arguments (source, start and
> length),
> with the latter two always unsigned int, while our intrinsic has only two
> arguments (where the latter is expected to be (start & 255) | (length << 8)).
> Not sure if we want to change this, and if so, just for 4.9+, or also for
> 4.8.2+ and 4.7.4+?

If you decide to change it, at least consider keeping the old version around;
for instance, the start/length combination could come from a table. In
general, if you actually have to do shifting and stuff to create this
operand, the gain of the instruction is already lost.

/* Steinar */


  parent reply	other threads:[~2013-06-15 17:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-15 14:29 [Bug target/57623] New: " sgunderson at bigfoot dot com
2013-06-15 16:33 ` [Bug target/57623] " jakub at gcc dot gnu.org
2013-06-15 17:01 ` sgunderson at bigfoot dot com [this message]
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-GwtB3Lj1Kl@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).