This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Internal abort call optimization?
- From: "Richard Guenther" <richard dot guenther at gmail dot com>
- To: "Andi Kleen" <andi at firstfloor dot org>
- Cc: "David Kastrup" <dak at gnu dot org>, gcc at gnu dot org
- Date: Tue, 17 Jun 2008 12:02:50 -0400
- Subject: Re: Internal abort call optimization?
- References: <86abhki2n0.fsf@lola.quinscape.zz> <87skvcvzxi.fsf@basil.nowhere.org>
On Tue, Jun 17, 2008 at 11:33 AM, Andi Kleen <andi@firstfloor.org> wrote:
> David Kastrup <dak@gnu.org> writes:
>>
>> However, the problem is obviously not restricted to Emacs. If the
>> "noreturn" attribute for the internal abort were removed, at least only
>> abort calls with compatible stack frame and the same (tentative)
>> followup code would get folded. That would avoid the worst
>> head-scratchers when trying to figure out what went wrong.
>
> Without noreturn gcc wouldn't know there is no return needed after
> the abort(). Disabling cross jumping would be probably better.
> I know of a couple of more cases where such an attribute would
> be useful.
You can also build with -fno-builtin-abort.
Richard.