Re: [PATCH] gcc-3.0.1 and 2.4.7-ac1

From: Florian Weimer (Florian.Weimer@RUS.Uni-Stuttgart.DE)
Date: Fri Jul 27 2001 - 11:03:17 EST

Next message: Henning P. Schmiedehausen: "Re: ReiserFS / 2.4.6 / Data Corruption"
Previous message: Steve Underwood: "Re: Hard disk problem:"
In reply to: Petr Vandrovec: "Re: [PATCH] gcc-3.0.1 and 2.4.7-ac1"
Next in thread: Petr Vandrovec: "Re: [PATCH] gcc-3.0.1 and 2.4.7-ac1"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

"Petr Vandrovec" <VANDROVE@vc.cvut.cz> writes:

> Just adding '-finline-limit=150' fixes all of them

This is not a fix, this is a workaround which is suitable for some
specific GCC release(s). The optimization decisions surrounding
inlining are likely to change again, so this will break almost
certainly in the future.

At least one GCC frontend has got a pragma called Always_Inline. This
seems the way to go. For the C frontend, you would use a function
attribute, of course.

-- 
Florian Weimer 	                  Florian.Weimer@RUS.Uni-Stuttgart.DE
University of Stuttgart           http://cert.uni-stuttgart.de/
RUS-CERT                          +49-711-685-5973/fax +49-711-685-5898
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Next message: Henning P. Schmiedehausen: "Re: ReiserFS / 2.4.6 / Data Corruption"
Previous message: Steve Underwood: "Re: Hard disk problem:"
In reply to: Petr Vandrovec: "Re: [PATCH] gcc-3.0.1 and 2.4.7-ac1"
Next in thread: Petr Vandrovec: "Re: [PATCH] gcc-3.0.1 and 2.4.7-ac1"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Tue Jul 31 2001 - 21:00:33 EST