This is the mail archive of the
mailing list for the GCC project.
Re: [tree-ssa/mainline] PR 14756
- From: Jan Hubicka <hubicka at ucw dot cz>
- To: Zack Weinberg <zack at codesourcery dot com>
- Cc: Jan Hubicka <jh at suse dot cz>, gcc-patches at gcc dot gnu dot org, rth at redhat dot com
- Date: Sun, 28 Mar 2004 19:26:04 +0200
- Subject: Re: [tree-ssa/mainline] PR 14756
- References: <20040328170916.GG24463@kam.mff.cuni.cz> <email@example.com>
> Jan Hubicka <firstname.lastname@example.org> writes:
> > Hi,
> > the error is quite right about the fact that called function is not
> > being considered for inlining. The function is not inline function, but
> > in the macro call it is casted to inline function, so we get the warning
> > output.
> > This patch makes the errors/warnings to be controlled by the function
> > type, not the type it has been possibly casted to.
> That sounds right to me.
> > Zack, perhaps we should issue warning when casting non-inlie to inline
> > and error when casting non-always-inline to always-inline?
> Why are casts which add/remove 'inline' allowed *at all*?
I am not sure. Outputting hard errors would be fine to me too. I guess
it depends on what C standard thinks here.
> > init_dummy_function_start ();
> > init_expmed ();
> > + init_optimization_passes ();
> > if (flag_caller_saves)
> > init_caller_save ();
> > expand_dummy_function_end ();
> Isn't init_optimization_passes now being called twice?
hubicka@kampanus:/aux/hubicka/egcs4/gcc/gcc$ grep init_optimization_passes *.c *.h
toplev.h:extern void init_optimization_passes (void);