search for: annecdotal

...to relegate "inline" to the same status as "register" -- an obsolete hint ignored by the compiler -- and so far that always proved to be unpractical because some critical calls that were previously inlined were no longer being inlined after the change. (That's just annecdotal, of course: LLVM may have gotten good enough to make it practical. If that's the case, I still think it's too early to write C ++ code with that assumption.) Daveed

..."inline" to the same status as "register" -- an > obsolete hint ignored by the compiler -- and so far that always proved > to be unpractical because some critical calls that were previously > inlined were no longer being inlined after the change. (That's just > annecdotal, of course: LLVM may have gotten good enough to make it > practical. If that's the case, I still think it's too early to > write C > ++ code with that assumption.) It's actually the other way around. llvm has always ignored the "inline" keyword and now we are fi...

On Aug 26, 2009, at 12:01 PM, Devang Patel wrote: >>> I do not understand how the "inlinehint" will help. How will it >>> influence the inliner ? >> >> The hint should make it more attractive to inline. I don't know >> the details >> yet and they will require some experimenting. >> > > In that case you want to add hint to A

...ot; to the same status as "register" -- an >> obsolete hint ignored by the compiler -- and so far that always proved >> to be unpractical because some critical calls that were previously >> inlined were no longer being inlined after the change.  (That's just >> annecdotal, of course: LLVM may have gotten good enough to make it >> practical.  If that's the case, I still think it's too early to >> write C >> ++ code with that assumption.) > > It's actually the other way around. llvm has always ignored the > "inline" key...

...nline" to the same status as "register" -- an > obsolete hint ignored by the compiler -- and so far that always proved > to be unpractical because some critical calls that were previously > inlined were no longer being inlined after the change. (That's just > annecdotal, of course: LLVM may have gotten good enough to make it > practical. If that's the case, I still think it's too early to write C > ++ code with that assumption.) > There is often a keyword force_inline or alwais_inline if needed Cédric

...ame status as "register" -- >> an obsolete hint ignored by the compiler -- and so far that always >> proved to be unpractical because some critical calls that were >> previously inlined were no longer being inlined after the change. >> (That's just annecdotal, of course: LLVM may have gotten good >> enough to make it practical. If that's the case, I still think >> it's too early to write C ++ code with that assumption.) >> > > There is often a keyword force_inline or alwais_inline if needed Yes, but that's not...

...same status as "register" -- an >> obsolete hint ignored by the compiler -- and so far that always >> proved >> to be unpractical because some critical calls that were previously >> inlined were no longer being inlined after the change. (That's just >> annecdotal, of course: LLVM may have gotten good enough to make it >> practical. If that's the case, I still think it's too early to >> write C >> ++ code with that assumption.) > > It's actually the other way around. llvm has always ignored the > "inline" key...

This is a follow-up announcement from the 0.9 release. There are no major changes, but this release marks a downloadable (tgz) file as well as a promotional website, a demo application and screenshots. Family Connection is an easy-to-setup online hub for your family that includes a Family News section, and an Address Book. http://familyconnect.rubyforge.org/ Please note that the download