This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Fix build warnings in regex.c, bug-regex20.c, bug-regex33.c

From: Siddhesh Poyarekar <siddhesh at redhat dot com>
To: Thomas Schwinge <thomas at codesourcery dot com>
Cc: libc-alpha at sourceware dot org
Date: Thu, 14 Feb 2013 17:20:08 +0530
Subject: Re: [PATCH] Fix build warnings in regex.c, bug-regex20.c, bug-regex33.c
References: <20130214060403.GB15748@spoyarek.pnq.redhat.com><87zjz7m8jy.fsf@kepler.schwinge.homeip.net>

On Thu, Feb 14, 2013 at 12:36:17PM +0100, Thomas Schwinge wrote:
> Wouldn't marking them as always_inline (which is the intention here, I
> think?) also make that warning go away?
> 

It would have, but gcc thinks that those functions are not inlinable:

In file included from regex.c:63:0:
regex_internal.h:740:1: warning: always_inline function might not be inlinable [-Wattributes]
regex_internal.h:730:1: warning: always_inline function might not be inlinable [-Wattributes]
regex_internal.h:717:1: warning: always_inline function might not be inlinable [-Wattributes]
regex_internal.h:706:1: warning: always_inline function might not be inlinable [-Wattributes]
regex_internal.h:698:1: warning: always_inline function might not be inlinable [-Wattributes]
regex_internal.h:690:1: warning: always_inline function might not be inlinable [-Wattributes]


Siddhesh

References:
- [PATCH] Fix build warnings in regex.c, bug-regex20.c, bug-regex33.c
  - From: Siddhesh Poyarekar
- Re: [PATCH] Fix build warnings in regex.c, bug-regex20.c, bug-regex33.c
  - From: Thomas Schwinge

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]