public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "david.bolvansky at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/104187] Call site specific attribute to control inliner
Date: Thu, 03 Mar 2022 10:23:52 +0000	[thread overview]
Message-ID: <bug-104187-4-tOWv4sNwPg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104187-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Dávid Bolvanský <david.bolvansky at gmail dot com> ---
So this works in Clang now

int foo(int x, int y) { // any compiler will happily inline this function
    return x / y;
}

int test(int x, int y) {
    int r = 0;
    [[clang::noinline]] r += foo(x, y); // for some reason we don't want any
inlining here
    return r;
}


foo(int, int): # @foo(int, int)
  mov eax, edi
  cdq
  idiv esi
  ret
test(int, int): # @test(int, int)
  jmp foo(int, int) # TAILCALL

foo(int, int): # @foo(int, int)
  mov eax, edi
  cdq
  idiv esi
  ret
test(int, int): # @test(int, int)
  jmp foo(int, int) # TAILCALL

      parent reply	other threads:[~2022-03-03 10:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-22 16:15 [Bug c/104187] New: " david.bolvansky at gmail dot com
2022-01-22 17:46 ` [Bug ipa/104187] " pinskia at gcc dot gnu.org
2022-01-24  7:49 ` marxin at gcc dot gnu.org
2022-01-24  9:13 ` rguenth at gcc dot gnu.org
2022-01-24  9:19 ` pinskia at gcc dot gnu.org
2022-01-24 10:18 ` hubicka at kam dot mff.cuni.cz
2022-01-24 22:35 ` joseph at codesourcery dot com
2022-01-25 20:30 ` david.bolvansky at gmail dot com
2022-01-26 13:22 ` hubicka at gcc dot gnu.org
2022-02-10 13:02 ` aaron at aaronballman dot com
2022-03-03 10:23 ` david.bolvansky at gmail dot com [this message]

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-104187-4-tOWv4sNwPg@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).