search for: prorotyp

...redefine it from historical anachronism to architectural flag, that indicates you may generate more code with the same functions and globals later? And then, you could pass the same flag to createStandardLTOPasses, and that would skip the GlobalDCE passes. >> Even then, my runtime function prorotypes are still being stripped away by the GlobalDCE added by createStandardLTOPasses. > > Sure, and why not? Unused prototypes are not used for anything, they won't > turn up in the generated code for example. They are not used this time. But why can't I generate additional code in...

...he StripDeadPrototypesPass was removing all references to my runtime support functions. Apparently, this depends on the oddly-named UnitAtATime parameter. Set it to false. Try again. Suggestion: what about a comment explaining what "UnitAtATime" means :-) Even then, my runtime function prorotypes are still being stripped away by the GlobalDCE added by createStandardLTOPasses. So my question is: what is the correct, officially recommended way to reference runtime functions so that global DCE won't get rid of them? Or am I supposed to re-create the corresponding Function instances for...

...skip the GlobalDCE passes. LTO is for doing optimizations that are only valid when the module contains everything that is needed to build the final executable. So adding a flag to say "not everything is there after all" makes no sense to me. >>> Even then, my runtime function prorotypes are still being stripped away by the GlobalDCE added by createStandardLTOPasses. >> >> Sure, and why not? Unused prototypes are not used for anything, they won't >> turn up in the generated code for example. > > They are not used this time. But why can't I generat...

...nitAtATime is false this means that you are optimizing functions as you are generating them, rather than first generating all functions and other globals and only then optimizing. It's basically a historical anachronism coming from the way GCC used to work. > Even then, my runtime function prorotypes are still being stripped away by the GlobalDCE added by createStandardLTOPasses. Sure, and why not? Unused prototypes are not used for anything, they won't turn up in the generated code for example. > So my question is: what is the correct, officially recommended way to reference runtim...

...flag to > say "not everything is there after all" makes no sense to me. And indeed, everything is there when I call LTO. The flag is not "not everything is there after all", but "don't damage your inputs". > >>>> Even then, my runtime function prorotypes are still being stripped away by the GlobalDCE added by createStandardLTOPasses. >>> >>> Sure, and why not? Unused prototypes are not used for anything, they won't >>> turn up in the generated code for example. >> >> They are not used this time. But w...

I'm trying to build 3.0.30 on Alpha/Tru64-4.0G. The configure step works, but make fails when it tries to link smbd: Compiling popt/popt.c Compiling popt/poptconfig.c Compiling popt/popthelp.c Compiling popt/poptparse.c Linking bin/smbd ld: Unresolved: __unsafe_string_function_usage_here_size_t__ gmake: *** [bin/smbd] Error 1 This Should Never Happen :) -- that looks like a message for the