Messages in this thread | | | Date | Tue, 31 Aug 2004 16:01:13 -0700 | From | Andrew Morton <> | Subject | Re: [2.6 patch] kill __always_inline |
| |
Adrian Bunk <bunk@fs.tum.de> wrote: > > If you want to change inline at some point, you will have to audit all > users of inline anyway - so why bother if you don't intend to change > inline in the forseeable future?
inline was set to do `always inline' when it was discovered that new gcc was doing dopey things. If gcc gets fixed then we don't need that any more.
But functions which *must* be inlined should be marked __always_inline regardless of anything else. - 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/
| |