public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan Hubicka <hubicka@ucw.cz>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Alexander Monakov <amonakov@ispras.ru>,
	Michael Matz <matz@suse.de>,
	gcc-patches@gcc.gnu.org
Subject: Re: [x86-64] RFC: Add nosse abi attribute
Date: Tue, 11 Jul 2023 10:53:18 +0200	[thread overview]
Message-ID: <ZK0YfliCddgAlfIn@kam.mff.cuni.cz> (raw)
In-Reply-To: <CAFiYyc2hiZjYc=4yEtq=QgchVTo_2+WJKEJFyahjaVaBLwwMow@mail.gmail.com>

> > > FWIW, this particular patch was regstrapped on x86-64-linux
> > > with trunk from a week ago (and sniff-tested on current trunk).
> >
> > This looks really cool.
> 
> The biggest benefit might be from IPA with LTO where we'd carefully place those
> attributes at WPA time (at that time tieing our hands for later).

Within single partition IRA already propagates the knowledge about
callee-clobbered registers.

Across partition we already automatically enable regparm with -m32
see ix86_function_regparm and tests for target->local and
can_change_attribute

Enabling SSE at the same spot should be easy.

Honza

  reply	other threads:[~2023-07-11  8:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10 15:55 Michael Matz
2023-07-10 17:28 ` Richard Biener
2023-07-10 19:07 ` Alexander Monakov
2023-07-10 20:33   ` Alexander Monakov
2023-07-11  6:42   ` Richard Biener
2023-07-11  8:53     ` Jan Hubicka [this message]
2023-07-11  9:07       ` Richard Biener
2023-07-11 13:00   ` Richard Biener
2023-07-11 13:21     ` Jan Hubicka
2023-07-11 14:00       ` Michael Matz
2023-07-11 13:59     ` Alexander Monakov
2023-07-11 14:57   ` Michael Matz
2023-07-11 15:17     ` Alexander Monakov
2023-07-11 15:34       ` Michael Matz
2023-07-11 16:53         ` Alexander Monakov
2023-07-17 23:00 ` Richard Sandiford

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=ZK0YfliCddgAlfIn@kam.mff.cuni.cz \
    --to=hubicka@ucw.cz \
    --cc=amonakov@ispras.ru \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=matz@suse.de \
    --cc=richard.guenther@gmail.com \
    /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).