public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/116497] Need no_caller_saved_registers with SSE support
Date: Tue, 27 Aug 2024 16:25:14 +0000	[thread overview]
Message-ID: <bug-116497-4-oblXxDwWiq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-116497-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #17 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Andi Kleen from comment #16)
> Created attachment 59013 [details]
> test case
> 
> This test case using Pinski's clobber trick shows the benefit.
> 
> If you compile with -O2 -mgeneral-regs-only the inc/dec opcodes don't save
> any extra registers and generate nearly optimal code. If you make the
> SAVE_REGS/DONT_SAVE_REGS macros empty they have a lot of extra push/pop,
> which would ruin the interpreter loop.
> 
> -mgeneral-regs-only works for this case, but breaks SSE.

Why is __attribute__((no_caller_saved_registers)) needed on start?

  parent reply	other threads:[~2024-08-27 16:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-27  5:42 [Bug target/116497] New: " andi-gcc at firstfloor dot org
2024-08-27  5:49 ` [Bug target/116497] " andi-gcc at firstfloor dot org
2024-08-27  5:50 ` pinskia at gcc dot gnu.org
2024-08-27  5:58 ` [Bug target/116497] static functions ABI should be improved for SSE caller saved registers pinskia at gcc dot gnu.org
2024-08-27  6:03 ` pinskia at gcc dot gnu.org
2024-08-27  6:17 ` andi at firstfloor dot org
2024-08-27  6:25 ` [Bug target/116497] Need no_caller_saved_registers with SSE support pinskia at gcc dot gnu.org
2024-08-27  7:58 ` liuhongt at gcc dot gnu.org
2024-08-27  8:02 ` rguenth at gcc dot gnu.org
2024-08-27  8:10 ` andi at firstfloor dot org
2024-08-27  8:14 ` andi at firstfloor dot org
2024-08-27  8:26 ` xry111 at gcc dot gnu.org
2024-08-27 13:27 ` hjl.tools at gmail dot com
2024-08-27 14:21 ` andi at firstfloor dot org
2024-08-27 14:33 ` andi at firstfloor dot org
2024-08-27 14:47 ` pinskia at gcc dot gnu.org
2024-08-27 15:19 ` hjl.tools at gmail dot com
2024-08-27 15:53 ` andi-gcc at firstfloor dot org
2024-08-27 16:25 ` hjl.tools at gmail dot com [this message]
2024-08-27 17:06 ` andi at firstfloor dot org
2024-08-27 17:12 ` hjl.tools at gmail dot com
2024-08-27 17:49 ` andi at firstfloor dot org
2024-08-27 17:50 ` andi-gcc at firstfloor dot org
2024-08-27 17:50 ` andi-gcc at firstfloor dot 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-116497-4-oblXxDwWiq@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).