>
> They're added to the cgraph by this call:
>
> /* Add to cgraph. */
> cgraph_node::finalize_function (fndecl, false);
>
> within function_reader::create_function (in r244110, though that code
> isn't called yet; it's called by the stuff in patch 9).
>
> If I hack out that call, so that
On 01/17/2017 02:21 AM, Richard Biener wrote:
So I guess my question is how do you ensure that even though cgraph hasn't
looked at code that we're appropriately conservative with how the file is
processed? Particularly if there's other code in the source file that is
expected to interact with
On Tue, 2017-01-17 at 13:35 +0100, Jan Hubicka wrote:
> > On Mon, Jan 16, 2017 at 10:25 PM, Jeff Law wrote:
> > > On 01/09/2017 07:38 PM, David Malcolm wrote:
> > > >
> > > > The RTL backend code is full of singleton state, so we have to
> > > > handle
> > > > functions as soon
> On Mon, Jan 16, 2017 at 10:25 PM, Jeff Law wrote:
> > On 01/09/2017 07:38 PM, David Malcolm wrote:
> >>
> >> The RTL backend code is full of singleton state, so we have to handle
> >> functions as soon as we parse them. This requires various special-casing
> >> in the
On Mon, Jan 16, 2017 at 10:25 PM, Jeff Law wrote:
> On 01/09/2017 07:38 PM, David Malcolm wrote:
>>
>> The RTL backend code is full of singleton state, so we have to handle
>> functions as soon as we parse them. This requires various special-casing
>> in the callgraph code.
>>
On 01/09/2017 07:38 PM, David Malcolm wrote:
The RTL backend code is full of singleton state, so we have to handle
functions as soon as we parse them. This requires various special-casing
in the callgraph code.
gcc/ChangeLog:
* cgraph.h (symtab_node::native_rtl_p): New decl.
*
The RTL backend code is full of singleton state, so we have to handle
functions as soon as we parse them. This requires various special-casing
in the callgraph code.
gcc/ChangeLog:
* cgraph.h (symtab_node::native_rtl_p): New decl.
* cgraphunit.c (symtab_node::native_rtl_p): New