Re: [2.1.90][PATCH] Cleaning up linux-2.1.90.

Alan Cox (alan@lxorguk.ukuu.org.uk)
Thu, 19 Mar 1998 11:18:44 +0000 (GMT)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Niels Kristian Bech Jensen: "Re: is gcc 2.8 safe to use yet ?"
Previous message: Marek Habersack: "Re: is gcc 2.8 safe to use yet ?"
In reply to: Daniel Egger: "Re: [2.1.90][PATCH] Cleaning up linux-2.1.90."

> >But in the case of exit the procedure end is never reached.
> >If the prototype of exit is correctly marked as noreturn
> >(extern void exit(int) __attribute__ ((noreturn));) then
> >gcc won't barf.
>
> Yeah, but other compilers will probably not compile that construct...
>

Which is why its __attribute(x)__ - anything beginning __ is compiler
depenant. It also means you can #define __attribute(x)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

Next message: Niels Kristian Bech Jensen: "Re: is gcc 2.8 safe to use yet ?"
Previous message: Marek Habersack: "Re: is gcc 2.8 safe to use yet ?"
In reply to: Daniel Egger: "Re: [2.1.90][PATCH] Cleaning up linux-2.1.90."