DECL_RTL vs. explicit make_decl_rtl calls
Richard Henderson
rth@redhat.com
Thu Jun 13 08:57:00 GMT 2002
On Thu, Jun 13, 2002 at 02:56:39AM -0700, David S. Miller wrote:
> 1) ENCODE_SECTION_INFO, in several backends, expect that it will be
> called on each function declaration. It also wants to have the
> DECL_RTL() formed by the time it is called so Richard's idea
> of just calling ENCODE_SECTION_INFO directly won't work.
[...]
> Now, thinking more about #1 it really shouldn't matter. If we were to
> omit these explicit make_decl_rtl calls we would end up calling
> ENCODE_SECTION_INFO if we ever try to get at the DECL_RTL.
Except when the DECL_RTL already exists. You don't want to
elide the call to ENCODE_SECTION_INFO in that case.
> There is also a bunch of stuff in make_decl_rtl dealing with mode
> changes if we've got the DECL_RTL already. Does this really happen?
Yes. Incomplete types and all that.
r~
More information about the Gcc
mailing list