statement expressions and extended asm bug?

[Gunther Nikl]

On Mon, Mar 15, 2004 at 08:51:58PM +0000, Jamie Lokier wrote:
> Gabriel Dos Reis wrote:
> > | Perhaps this is a flaw in GCC's implementation of
> > | statement-expression, because s-e is intended for use in macros
> > | function-like macros -- whose callers don't know they are calling a
> > | macro.

  That was the motivation: function-like macros.

> > Well, that is called inline functions :-)
> 
> Yes, but as the primary reason for statement expressions is to make
> macros that can be called like functions, and there are vast numbers
> of macros written using that assumption, perhaps the preferred semantic
> is that they behave like it :)

  Does that mean the current 3.3+ behaviour regarding s-e is a bug?
  If thats the case, shall I file a pr?

> > If you consistently and predictably inline functions, people won't
> > ddamage their codes and run into troubles -- even if "they asked for it". 
> 
> Yes.
> That is preferable now that the inliner is better than it used to be.

  How well does that work in contrast to s-e? In my case the preprocessor
  did most of the work, that is the compiler saw only the really used
  "functions". With inlining the compiler has to parse all inline
  functions even if most of them won't be used at all.

  Gunther