public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Christian Bruel <christian.bruel@st.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,	Jan Hubicka <hubicka@ucw.cz>
Subject: Re: [PATH] PR/49139 fix always_inline failures diagnostics
Date: Wed, 08 Jun 2011 08:25:00 -0000	[thread overview]
Message-ID: <4DEF28F0.6080300@st.com> (raw)
In-Reply-To: <BANLkTikGR-fr04FaDyTyS6tYw1-cYsQgZQ@mail.gmail.com>

Hello Richard,

On 06/06/2011 11:55 AM, Richard Guenther wrote:
> On Mon, Jun 6, 2011 at 10:58 AM, Christian Bruel<christian.bruel@st.com>  wrote:
>>
>>
>>>> OK, the only difference is that we don't have the node analyzed here, so
>>>> externally_visible, etc are not set. With the initial proposal the
>>>> warning
>>>> was emitted only if the function could not be inlined. Now it will be
>>>> emitted for each  DECL_COMDAT (decl)&&    !DECL_DECLARED_INLINE_P (decl))
>>>> even
>>>> if not preemptible, so conservatively we don't want to duplicate the
>>>> availability check.
>>>
>>> Hm, I'm confused.  Do all DECL_COMDAT functions have the
>>> always_inline attribute set?  I would have expected
>>>
>>> +      if (lookup_attribute ("always_inline", DECL_ATTRIBUTES (decl)))
>>> +       {
>>> +         if (!DECL_DECLARED_INLINE_P (decl))
>>> +           warning (OPT_Wattributes,
>>> +                    "always_inline not declared inline might not be
>>> inlinable");
>>> +       }
>>>
>>
>> I meant !DECL_COMDAT || !DECL_DECLARED_INLINE_P. but I was overprecautious.
>> Didn't realize that member functions was already marked with
>> DECLARED_INLINED_P even if not explicitly set. So OK one check is enough
>>
>>> do you get excessive warnings with this?
>>>
>>
>> No I don't. That's enough to catch the original issue
>

Unfortunately still not satisfactory, I've been testing it against a few 
packages, and I notice excessive warnings with the use of __typeof 
(__error) that doesn't propagate the inline keyword.

For instance, a reduced use extracted from the glibc

extern __inline __attribute__ ((__always_inline__))  void
error ()
{

}

extern void
__error ()
{
}

extern __typeof (__error) error __attribute__ ((weak, alias ("__error")));

emits an annoying warning on the error redefinition.

So, a check in addition of the DECL_DECLARED_INLINED_P is needed, 
TREE_ADDRESSABLE seems appropriate, since in the case of missing inline 
the function would be emitted. So I'm testing:

if (lookup_attribute ("always_inline", DECL_ATTRIBUTES (decl))
	  && !DECL_DECLARED_INLINE_P (decl)
	  && TREE_ADDRESSABLE (decl))

other idea ? or should be just drop this warning ?

> Ok.  The patch is ok with the !DECL_DECLARED_INLINE_P check
> if it still passes bootstrap&  regtest.
>

thanks, for now I postpone until glibc is ok and more legacy checks.

Cheers

Christian

> Thanks,
> Richard.
>
>> Cheers
>>
>> Christian
>>
>

  reply	other threads:[~2011-06-08  7:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31  9:07 Christian Bruel
2011-05-31 12:25 ` Richard Guenther
2011-05-31 12:28   ` Jakub Jelinek
2011-05-31 17:07   ` Christian Bruel
2011-06-01 10:03     ` Richard Guenther
2011-06-01 13:02       ` Christian Bruel
2011-06-01 13:07         ` Richard Guenther
2011-06-06  8:58           ` Christian Bruel
2011-06-06  9:55             ` Richard Guenther
2011-06-08  8:25               ` Christian Bruel [this message]
2011-06-08  9:42                 ` Richard Guenther
2011-06-08 11:56                   ` Christian Bruel
2011-06-14 11:29                   ` Christian Bruel
2011-06-20 13:36                   ` Christian Bruel
2011-06-20 13:46                     ` Rainer Orth
2011-06-20 13:54                       ` Mike Stump
2011-06-20 14:04                       ` Christian Bruel
2011-06-21 11:52                         ` Richard Guenther
2011-06-21 12:07                           ` Richard Guenther
2011-06-20 13:51                     ` Richard Guenther
2011-06-01 14:49       ` Jan Hubicka

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=4DEF28F0.6080300@st.com \
    --to=christian.bruel@st.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --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).