On 07/19/2016 10:16 AM, Georg-Johann Lay wrote:
Done. Attached is the updated version of the change, log entry is the
same as before.
Johann
LGTM.
Bernd
On 18.07.2016 16:13, Bernd Schmidt wrote:
On 07/14/2016 05:11 PM, Georg-Johann Lay wrote:
The hook allows better diagnostics: The address spaces are registered
with c_register_addr_space and if the parser comes across an address
space it provides the hook with the needed information, in particu
On 07/14/2016 05:11 PM, Georg-Johann Lay wrote:
The hook allows better diagnostics: The address spaces are registered
with c_register_addr_space and if the parser comes across an address
space it provides the hook with the needed information, in particular
the location of the token so that the m
This adds a new hook that allows to emit better diagnostics if an address space
is used that's not available.
One solution would be no not register the address space with
c_register_addr_space but that gives ugly report like
error: expected '=', ',', ';', 'asm' or '__attribute__' before 'f321
