public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/101829] problems with inline + __attribute__ ((malloc (deallocator)))
Date: Mon, 09 Aug 2021 15:58:10 +0000	[thread overview]
Message-ID: <bug-101829-4-2TtGh0KE12@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101829-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Jan Hubicka <hubicka at ucw dot cz> ---
> It might be possible to inline such functions by creating a "stub" call either
> after or before the inlined function body where the "stub" would just be there
> to represent the attributes.
> 
> Say, inline a 'deallocator' fn
> 
>   my_free (x);
> 
> as
> 
>   <inlined impl>
>   .IFN_STUB_DEALLOCATE (x);
> 
> or sth like that where those stubs are removed after any diagnostics with
> regard to pairing of malloc/free have been issued (not sure where that
> currently
> happens).

We have similar issue with functions calling alloca (that we may inline
if was able to insert stack restore).  I was always lazy to implement
this since we need to also insert it on the EH cleanup edges, but
perhaps it is time to learn inliner about such tricks...

Honza

  parent reply	other threads:[~2021-08-09 15:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-09 10:33 [Bug middle-end/101829] New: " eggert at cs dot ucla.edu
2021-08-09 12:52 ` [Bug middle-end/101829] " rguenth at gcc dot gnu.org
2021-08-09 15:58 ` hubicka at ucw dot cz [this message]
2021-08-12 20:32 ` msebor 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-101829-4-2TtGh0KE12@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).