<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Mon, Aug 4, 2025 at 2:06 AM Jan Beulich <<a href="mailto:jbeulich@suse.com">jbeulich@suse.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 01.08.2025 16:54, Joel Sherrill wrote:<br>
> Hi<br>
> <br>
> Over at RTEMS, we have this bit of code which is included with every<br>
> build of RTEMS on all architectures. It is a special section to<br>
> auto-load pretty printing scripts.<br>
> <br>
> asm( \<br>
> ".pushsection \".debug_gdb_scripts\", \"MS\",@progbits,1\n" \<br>
> ".byte 4\n" \<br>
> ".ascii \"gdb.inlined-script\\n\"\n" \<br>
> ".ascii \"import sys\\n\"\n" \<br>
> ".ascii \"import os.path\\n\"\n" \<br>
> ".ascii \"sys.path.append(os.path.join(gdb.PYTHONDIR, 'rtems'))\\n\"\n" \<br>
> ".ascii \"import rtems.pprinter as pprinter\\n\"\n" \<br>
> ".byte 0\n" \<br>
> ".popsection\n" \<br>
> );<br>
> <br>
> On all ARM builds but no other architecture, we get this message:<br>
> <br>
> /tmp/ccVjIfxL.s: Assembler messages:<br>
> /tmp/ccVjIfxL.s:19: missing merge / string entity size, 1 assumed<br>
> <br>
> Any suggestions on what isn't 100% right?<br>
> <br>
> Also, analyzing build logs, I have noticed that the assembler uses<br>
> Warning not warning like GCC. This was surprising when I noticed<br>
> that my scripts never reported warnings from as. And in this case,<br>
> it is just a message. Isn't this a warning?<br>
<br>
Thing is that this particular diagnostic, from an assembler-internal pov,<br>
isn't a warning. While as_warn() and alike would emit "Warning: " as a<br>
prefix, it's as_tsktsk() here (the important difference here being that<br>
this way it doesn't "officially" count as a warning, and hence doesn't<br>
affect building with --fatal-warnings). Considering the comment ahead of<br>
it, making it also emit "Warning: " probably would be appropriate, though.<br>
Going through its uses (Arm in particular uses this a lot), I can spot a<br>
few which open-code the prefixing of "Warning: ", so some tidying would<br>
want doing at the same time (plus whatever testsuite fallout there might<br>
be).<br></blockquote><div><br></div><div>The code that started this was added by a GSoC participant last year.</div><div>None of us noticed the "message" because it didn't follow the pattern</div><div>we expected. It's recent and not a surprise we missed it. </div><div><br></div><div>We have another case where "Warning" is present in some PowerPC</div><div>exception helpers. That code hasn't changed since 2008 according to</div><div>git blame. I have no idea how long "as" has given that Warning. Clearly </div><div>it has slipped through for a while.</div><div><br></div><div>I'm not blaming this on anyone. RTEMS has 18 architecture ports with</div><div>all using multilibs even for 32/64 bit RISC-V and PowerPC. Personally,</div><div>I switched RTEMS to GNU tools around 1991-2. None of us ever noticed</div><div>these different messages. Admittedly, the individual BSP logs are too</div><div>large to look for issues by hand. We usually grep for "warning:" and clearly </div><div>that is insufficient. My point is that from a user perspective, it wasn't clear</div><div>we should also look for Warning and message.</div><div><br></div><div>We do see that tool updates trigger new warnings and we only </div><div>find those via reporting tools. I have augmented the search pattern to</div><div>include Warning and "assembler message".</div><div><br></div><div>If this was a small code base with only a few targets, I am sure these </div><div>messages would be spotted by hand. <br><br>Is this variance in diagnostics that anyone else has had issues because</div><div>of before us?</div><div><br></div><div>--joel</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Jan<br>
</blockquote></div></div>