> Yes, but...

I've committed the attached.

>>> +Any memory required by the @var{init} function should be allocated using
>>> +@var{gdbarch_obstack_zalloc}.
> 
> 
> `gdbarch_obstack_zalloc' is not a parameter, but a true literal
> symbol, so it should be in @code, not in @var.
> 
> 
>>>  @deftypefun void set_gdbarch_data (struct gdbarch *@var{gdbarch}, struct gdbarch_data *handle, void *@var{pointer})
> 
> 
> `handle' should be in @var here, I think.
> 
> 
>>> +Set the uninitialized (NULL) data-pointer corresponding to @var{handle}
>>> +to the non-NULL @var{pointer} value.
> 
> 
> Both `NULL's should be in @code.
> 
> Also, is it guaranteed that uninitialized pointers have a NULL value?
> In general, that's not true, but perhaps in the context of gdbarch it
> is, I just don't know.

I changed it to: "Set the still @code{NULL} data-pointer ..."

Andrew