Mike Stump writes:
> On Aug 23, 2012, at 1:30 PM, Richard Sandiford wrote:
>>> ../../gcc/gcc/target-globals.c: In function ‘target_globals*
>>> save_target_globals()’:
>>> ../../gcc/gcc/target-globals.c:69:33: error: ‘ggc_alloc_target_globals’ was
>>> not declared in this scope
>>> make: *** [ta
On Thu, Aug 23, 2012 at 02:29:39PM -0700, Mike Stump wrote:
> On Aug 23, 2012, at 1:30 PM, Richard Sandiford wrote:
> >> ../../gcc/gcc/target-globals.c: In function ‘target_globals*
> >> save_target_globals()’:
> >> ../../gcc/gcc/target-globals.c:69:33: error: ‘ggc_alloc_target_globals’
> >> was
On Aug 23, 2012, at 1:30 PM, Richard Sandiford wrote:
>> ../../gcc/gcc/target-globals.c: In function ‘target_globals*
>> save_target_globals()’:
>> ../../gcc/gcc/target-globals.c:69:33: error: ‘ggc_alloc_target_globals’ was
>> not declared in this scope
>> make: *** [target-globals.o] Error 1
>>
On Thu, Aug 23, 2012 at 1:30 PM, Richard Sandiford
wrote:
> Mike Stump writes:
>> On Jun 26, 2010, at 12:24 PM, Richard Sandiford wrote:
>>> GCC has a fair number of global variables that cache target-dependent
>>> data. This makes it difficult to switch between subtargets on the fly,
>>> such a
Mike Stump writes:
> On Jun 26, 2010, at 12:24 PM, Richard Sandiford wrote:
>> GCC has a fair number of global variables that cache target-dependent
>> data. This makes it difficult to switch between subtargets on the fly,
>> such as when switching between a MIPS16 and a non-MIPS16 function.
>>
On Jun 26, 2010, at 12:24 PM, Richard Sandiford wrote:
> GCC has a fair number of global variables that cache target-dependent
> data. This makes it difficult to switch between subtargets on the fly,
> such as when switching between a MIPS16 and a non-MIPS16 function.
>
> Our current approach is
