[debug-early] Handle specification of class scoped static functions
Jason Merrill
jason@redhat.com
Fri Apr 3 14:48:00 GMT 2015
On 03/20/2015 08:11 PM, Aldy Hernandez wrote:
> + /* For class scoped static functions, the dumped early
> + version was the declaration, whereas the next time
> + around with a different context should be the
> + specification. In this case, avoid reusing the DIE, but
> + generate a specification below. E.g.:
> +
> + class C {
> + public:
> + static void moo () {}
> + }; */
> + || !is_cu_die (context_die))
Why do we still need this added (relative to trunk)? Are we getting
here multiple times with class context_die?
Also, the comment seems redundant with the comment immediately above.
Jason
More information about the Gcc-patches
mailing list