From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Elizabeth Chastain <chastain@cygnus.com>
To: chastain@cygnus.com, shebs@apple.com
Cc: ac131313@cygnus.com, cagney@cygnus.com, gdb-patches@sourceware.cygnus.com, kettenis@wins.uva.nl, msnyder@cygnus.com
Subject: Re: [RFA] Testsuite addition for x86 linux GDB and SIGALRM fix
Date: Thu, 28 Jun 2001 13:02:00 -0000
Message-id: <200106282002.NAA29458@stanley.cygnus.com>
X-SW-Source: 2001-06/msg00474.html

Ah, I have an example in the existing test suite.

gdb.base/funcargs.c has several functions with one-line bodies:

  #ifdef PROTOTYPES
  void call5a (struct stag st)
  #else
  call5a (st)
  struct stag st;
  #endif
  {st.s1 = 5;}

In some configurations, this causes problems because gcc optimizes away
the stabn for the end of the prologue.  gdb needs that stabn; without
that stabn, it ultimately comes up with a bogus place to breakpoint and
thus prints incorrect values of the "st" argument.

I've seen this happen on native i686-pc-cygwin and native i686-pc-linux
with a gcc v2 compiler.  I haven't seen it happen with a gcc v3 compiler.
I haven't filed a bug report yet.

The bug depends on the fact that the whole function body is one line.
The Gnu Coding Standard prohibits this:

  http://www.gnu.org/prep/standards_22.html#SEC22

MichaelC