Date:	Sun, 15 Nov 1998 13:14:28 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Erik Max Francis <max AT alcyone DOT com>
cc:	djgpp AT delorie DOT com
Subject:	Re: size of a function in memory
In-Reply-To:	<364DF8E2.4266297@alcyone.com>
Message-ID:	<Pine.SUN.3.91.981115131406.1381V-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com

On Sat, 14 Nov 1998, Erik Max Francis wrote:

> Nate Eldredge wrote:
> 
> > Be aware that this is not portable.  It depends fairly strongly on
> > GCC's
> > compiling conventions and may fail on other compilers, or even some
> > future version of GCC.  If it's for something like memory locking that
> > isn't portable anyway, though, this probably isn't much of an issue.
> 
> I can't imagine why anyone would need to know the size of a function
> unless they were already planning on doing something extremely
> nonportable.

True, but this could also break with a new release of GCC, and you
would hardly want your code be dependent on a compiler version.

- Raw text -