search for: implicitinlin

...actually boring infrastructure, and you will note that > the actual consultation of the hints in InlineSimple.cpp is just a few lines > leaving much room for further improvements. Yup. >> Here are the specific problems with your patch that I see: >> >> 1. ExplicitInline/ImplicitInline are currently ignored. These fall into >> the class of dangerous information that is hard to use in a >> meaningful way. For example just becase a method is defined in the >> body of a class, it doesn't tell you anything about its potential for >> inlining...

...t: I can tell you worked hard on it, and it is nice work. Hopefully my previous email helps clarify my position about why I think these sorts of things are dangerous, and the ideas below will crystalize a way forward. Here are the specific problems with your patch that I see: 1. ExplicitInline/ImplicitInline are currently ignored. These fall into the class of dangerous information that is hard to use in a meaningful way. For example just becase a method is defined in the body of a class, it doesn't tell you anything about its potential for inlining: huge methods can be there too....