On Mon, 4 Aug 2025, David Faust wrote: > Hi Joseph, > > Could you please take a look at the front-end portion of this > series when you have a moment? > > New attributes/handlers - Patch 1: > https://gcc.gnu.org/pipermail/gcc-patches/2025-July/690142.html
It looks like the front-end code would accept wide strings (wchar_t, char16_t, char32_t), but the code actually processing the tags in dwarf2out.c expects narrow strings only. > Docs - Patch 5: > https://gcc.gnu.org/pipermail/gcc-patches/2025-July/690147.html > +int * __attribute__ ((btf_type_tag ("__user"))) foo; > +@end smallexample > + > +@noindent > +when compiled with @code{-gbtf} results in an additional > +@code{BTF_KIND_TYPE_TAG} BTF record to be emitted in the BTF info, > +associating the string ``__user'' with the normal @code{BTF_KIND_PTR} Command-line option names should be marked up with @option{}. It seems __user is literal source code text, so @samp{__user} is more appropriate than ``__user''. -- Joseph S. Myers josmy...@redhat.com
