Help with Warning on ARM

[Jan Beulich]

On 01.08.2025 16:54, Joel Sherrill wrote:
> Hi
> 
> Over at RTEMS, we have this bit of code which is included with every
> build of RTEMS on all architectures. It is a special section to
> auto-load pretty printing scripts.
> 
> asm( \
>   ".pushsection \".debug_gdb_scripts\", \"MS\",@progbits,1\n" \
>   ".byte 4\n" \
>   ".ascii \"gdb.inlined-script\\n\"\n" \
>   ".ascii \"import sys\\n\"\n" \
>   ".ascii \"import os.path\\n\"\n" \
>   ".ascii \"sys.path.append(os.path.join(gdb.PYTHONDIR, 'rtems'))\\n\"\n" \
>   ".ascii \"import rtems.pprinter as pprinter\\n\"\n" \
>   ".byte 0\n" \
>   ".popsection\n" \
>   );
> 
> On all ARM builds but no other architecture, we get this message:
> 
> /tmp/ccVjIfxL.s: Assembler messages:
> /tmp/ccVjIfxL.s:19: missing merge / string entity size, 1 assumed
> 
> Any suggestions on what isn't 100% right?
> 
> Also, analyzing build logs, I have noticed that the assembler uses
> Warning not warning like GCC. This was surprising when I noticed
> that my scripts never reported warnings from as. And in this case,
> it is just a message.  Isn't this a warning?

Thing is that this particular diagnostic, from an assembler-internal pov,
isn't a warning. While as_warn() and alike would emit "Warning: " as a
prefix, it's as_tsktsk() here (the important difference here being that
this way it doesn't "officially" count as a warning, and hence doesn't
affect building with --fatal-warnings). Considering the comment ahead of
it, making it also emit "Warning: " probably would be appropriate, though.
Going through its uses (Arm in particular uses this a lot), I can spot a
few which open-code the prefixing of "Warning: ", so some tidying would
want doing at the same time (plus whatever testsuite fallout there might
be).

Jan