This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC 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: Merging calls to `abort'



On 2005-03-14, at 05:20, Gary Funck wrote:



Richard Stallman wrote (in part):
What's the point of cross-jumping?  It saves a certain amount of
space; it has no other benefit.  All else being equal, there's no
reason not to do it.  But cross-jumping abort calls interferes with
debugging.  That's a good reason not to do it.
t's get rid of this optimization. Those who want to use a
fancy_abort function will still be able to do so, but this change will
be an improvement for the rest.

Would a new attribute be in order, that disables the optimization? For example, __attribute__ ((unique_call))? That way, the programmer can designate other procedures than abort() as procedures which should not be cross-jumped.

This may be generally useful. But in this particular case the meaning of
the function in question is already well defined by the standard. Thus it shouldn't
be required in esp. in lieu of the fact that not everybody is going to use a still
not existent version of glibc which may catch up in about est. 4 years on this.



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