This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: precompiled header support
In article <m3pt9923bt.fsf@gossamer.airs.com> you write:
>Gunther Nikl <gni@gecko.de> writes:
>
>> > Create a host-amiga.c file, mention it in config.host, and define
>> > HOST_HOOKS_GT_PCH_GET_ADDRESS to a function which simply calls
>> > error().
>>
>> That looks like a good solution. I just noticed that the PCH support in
>> 3.4.0 and mainline is different. Mainline will probably fail because
>> default_gt_pch_use_address would return -1. Hm, I suppose taht function
>> should simply return -1 and not allocate any memory. Its highly unlikely
>> that base and addr will ever match with the default_gt_pch_get_address.
>
>Yes, the default versions of the host hook, if you don't have mmap,
>will essentially always fail. I guess the effect on mainline is that
>you will be able to create a PCH on the Amiga, but you will never be
>able to use it.
>
>The default host hooks do the right thing if anybody implements the
>pointer swizzling required to avoid the "had to relocate PCH" error.
>I think that is what will be needed on the Amiga.
On the other hand, you can have resident stuff. If you want PCH stuff,
just hook it up at one given address, and never let go.
If you want to preserve it through system reboots, just reserve it from
start-up, that's how persistent ram-disks work on that machine.
I haven't played with an amiga for a few years, but last I remember, I
was almost forced to install a vmem handler to use gcc---it gobbles
insane amounts of memories, compared to most amiga `in-use' (I had 16M
of memory, which was quite a hefty amount)---that, plus a somewhat
unstable stack auto-extender, meant gcc never really flew on that
machine.
I really have trouble seeing a recent gcc being useful on that class of
machine, unless it has a heck of a lot more memory than I had, or unless
some kind of vmem handler has been installed...