public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "alex.popov at linux dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/96061] Please support 'no_caller_saved_registers' attribute on aarch64 (or maybe on all targets)
Date: Sat, 04 Jul 2020 22:01:06 +0000	[thread overview]
Message-ID: <bug-96061-4-sfzFHQRsFO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96061-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Alexander Popov <alex.popov at linux dot com> ---
>> Could you explain the connection between your attribute for zeroing
>> registers and 'no_caller_saved_registers' attribute?
> 
> We are porting
> 
> https://gitlab.com/x86-gcc/gcc/-/tree/users/hjl/caller-saved/old
> 
> from x86 back-end to middle-end.  no_caller_saved_registers changes what
> registers zero_call_used_regs can do.  Move no_caller_saved_registers to
> middle-end has a direct impact on zero_call_used_regs implementation in
> middle-end.

Ok. So, as I can understand, your work will enable 'no_caller_saved_registers'
attribute for all architectures. Am I right?

If so, good luck to you! Looking forward to your results.

  parent reply	other threads:[~2020-07-04 22:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-04 13:36 [Bug target/96061] New: " alex.popov at linux dot com
2020-07-04 16:09 ` [Bug target/96061] " hjl.tools at gmail dot com
2020-07-04 17:03 ` alex.popov at linux dot com
2020-07-04 17:15 ` hjl.tools at gmail dot com
2020-07-04 21:01 ` alex.popov at linux dot com
2020-07-04 21:45 ` hjl.tools at gmail dot com
2020-07-04 22:01 ` alex.popov at linux dot com [this message]
2020-07-04 22:12 ` hjl.tools at gmail dot com
2021-12-15 11:13 ` pinskia 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-96061-4-sfzFHQRsFO@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).