https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45152
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Known to work|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45152
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
Sev
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45152
Andrew Pinski changed:
What|Removed |Added
Target|i686-pc-linux-gnu |
Last reconfirmed|2010-08-22 07:38:09
--- Comment #4 from hubicka at ucw dot cz 2010-08-22 12:29 ---
Subject: Re: LTO breaks C99 inline
> It's equivalent - once the end of the translation unit is reached. But
> with C99 you can have the declaration with extern or without inline,
> coming *after* the definition, which is
> It's equivalent - once the end of the translation unit is reached. But
> with C99 you can have the declaration with extern or without inline,
> coming *after* the definition, which is what causes it to be exported.
OK,
is there any chance to convince the frontend to make the final representati
--- Comment #3 from joseph at codesourcery dot com 2010-08-22 12:12 ---
Subject: Re: LTO breaks C99 inline
On Sun, 22 Aug 2010, hubicka at gcc dot gnu dot org wrote:
> How this function is different from GNU C
> inline int f()
> alone? If it is equivalent, is there some chance that C
--- Comment #2 from hubicka at gcc dot gnu dot org 2010-08-22 07:38 ---
This is because C frontend implements this by calling
cgraph_mark_node_if_needed and the function ends up not being needed for LTO or
whole program.
This is a hack, since even if I make things needed, whole program w
