On Mon, 8 Dec 2014, Richard Biener wrote: > I'm not pushing this further for stage3, but for stage1 I'd like > to eventually address this by splitting up builtin_info_type's > 'implicit_p' into a flags array providing implicit_p, declared_p, > used_p and maybe declared_in_system_header_p. Would you be > willing to fill in the gap computing "used_p" in the C frontend?
C_DECL_USED is the right notion of "used" with the front end, in standard terms (i.e. the notion that requires a definition of the function to be present somewhere), though as noted some people may be relying on calls being optimized out. (Of course such people could get implicitly generated libm calls at present anyway; the point of checking "used" is to restrict call generation to cases where we know that some library with the function will be linked in, and that the function will have the right semantics.) -- Joseph S. Myers jos...@codesourcery.com
