public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ntukanov at cmu dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/102264] New: Macro Intrinsics fail to use all the registers on the machine
Date: Thu, 09 Sep 2021 20:43:34 +0000	[thread overview]
Message-ID: <bug-102264-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 102264
           Summary: Macro Intrinsics fail to use all the registers on the
                    machine
           Product: gcc
           Version: 9.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: inline-asm
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ntukanov at cmu dot edu
  Target Milestone: ---

I am trying to use custom intrinsics in order to have more control over the
assembly that the compiler is generating. The concept of these custom
intrinsics comes from http://users.ece.cmu.edu/~franzf/papers/wpmvp16.pdf.

For performance reasons, my code requires me to use all the available SIMD
registers on the machine, but when I use my custom intrinsics, I am only
getting half of the SIMD registers which leads to register spilling.

This is the code and generated assembly in question:
https://godbolt.org/z/fqn53G9qT

Any help would be greatly appericated.

             reply	other threads:[~2021-09-09 20:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-09 20:43 ntukanov at cmu dot edu [this message]
2021-09-09 21:12 ` [Bug inline-asm/102264] " pinskia at gcc dot gnu.org
2021-09-10  3:27 ` ntukanov at cmu dot edu
2021-09-10  7:49 ` [Bug target/102264] " rguenth at gcc dot gnu.org
2021-09-10  8:24 ` pinskia at gcc dot gnu.org
2021-09-10  8:42 ` [Bug target/102264] [9/10/11/12 Regression] extra spilling when using inline-asm and all registers pinskia at gcc dot gnu.org
2021-09-19 23:17 ` pinskia at gcc dot gnu.org
2022-01-20 10:14 ` rguenth at gcc dot gnu.org
2022-03-23  8:42 ` rguenth at gcc dot gnu.org
2022-05-27  9:46 ` [Bug target/102264] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:46 ` jakub at gcc dot gnu.org
2023-07-07 10:40 ` [Bug target/102264] [11/12/13/14 " rguenth at gcc dot gnu.org
2024-03-10  3:20 ` law at gcc dot gnu.org
2024-03-22 14:08 ` law 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-102264-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).