public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "siddhesh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/96503] attribute alloc_size effect lost after inlining
Date: Wed, 25 Oct 2023 13:40:31 +0000	[thread overview]
Message-ID: <bug-96503-4-x1S0UfuoMF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96503-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Siddhesh Poyarekar <siddhesh at gcc dot gnu.org> ---
(In reply to Martin Uecker from comment #7)
> For __builtin_with_access we probably only want to allow
> reducing the object size, while the 'extend_size' workaround 
> used by systemd (cf comment #4) would need to extend it. 
> Maybe we need another flag?

I've been thinking of a new __object_size__ attribute to annotate functions
that behave like __builtin_object_size so that calls to it override (and not
just reduce) sizes returned by allocations.  I can then use it to annotate a
supported malloc_usable_size replacement (say, malloc_size_estimate) that
actually works like __builtin_object_size and can then be used by systemd.

  parent reply	other threads:[~2023-10-25 13:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06 15:51 [Bug ipa/96503] New: " msebor at gcc dot gnu.org
2022-09-30  1:54 ` [Bug ipa/96503] " kees at outflux dot net
2022-11-18 23:57 ` pageexec at gmail dot com
2023-10-25  5:46 ` muecker at gwdg dot de
2023-10-25  5:54 ` sjames at gcc dot gnu.org
2023-10-25 10:55 ` siddhesh at gcc dot gnu.org
2023-10-25 11:08 ` siddhesh at gcc dot gnu.org
2023-10-25 13:03 ` muecker at gwdg dot de
2023-10-25 13:40 ` siddhesh at gcc dot gnu.org [this message]
2023-11-03 19:04 ` uecker 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-96503-4-x1S0UfuoMF@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).