public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "y.gribov at samsung dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/59600] no_sanitize_address mishandled when function is inlined
Date: Fri, 27 Dec 2013 05:07:00 -0000 [thread overview]
Message-ID: <bug-59600-4-P3FmY63BKs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59600-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59600
--- Comment #8 from Yury Gribov <y.gribov at samsung dot com> ---
Created attachment 31522
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31522&action=edit
Patch which inlines based on caller/callee attribute match
(In reply to Yury Gribov from comment #7)
> > And second you should compare the current function
> > attribute to fndecl attribute.
>
> You mean compare caller's and callee's attributes? Makes a lot of sense but
> I don't think this info is available at the time
> function_attribute_inlinable_p is called:
>
> ...
>
> Perhaps this check should be moved to e.g. expand_call_inline?
I'm giving this a try with this new patch. Does it look reasonable for you?
next prev parent reply other threads:[~2013-12-27 5:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-26 1:57 [Bug sanitizer/59600] New: " eggert at gnu dot org
2013-12-26 5:04 ` [Bug sanitizer/59600] " y.gribov at samsung dot com
2013-12-26 6:04 ` kcc at gcc dot gnu.org
2013-12-26 7:17 ` pinskia at gcc dot gnu.org
2013-12-26 7:24 ` pinskia at gcc dot gnu.org
2013-12-26 7:55 ` y.gribov at samsung dot com
2013-12-26 8:16 ` pinskia at gcc dot gnu.org
2013-12-27 5:07 ` y.gribov at samsung dot com [this message]
2014-02-05 5:23 ` ygribov at gcc dot gnu.org
2014-02-05 5:26 ` y.gribov at samsung dot com
2014-02-05 5:32 ` eggert at gnu dot 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-59600-4-P3FmY63BKs@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).