On Mon, May 18, 2026 at 6:31 PM Andrew Pinski <[email protected]> wrote: > > On Mon, May 18, 2026 at 3:53 AM Eric Botcazou <[email protected]> wrote: > > > > > This is what I've been discussing on IRC. Mangled names make it easier > > > to match -fstack-usage up to the symbol names output by avr-objdump and > > > similar tools. This is especially important on memory constrained > > > platforms like microcontrollers. > > > > Well, that's quite an incompatible change and the output was meant for human > > beings, not for scripts or LLMs, see the description of the manual. > > > > Please revert the change and/or devise something less incompatible. > > What about the attached patch which prints out both? > For an example with C++ code containing the function unopt that takes > an int argument and returns int, the output will be: > t.c:2:5:_Z5unopti `int unopt(int)` 16 static > > I actually can see the usefulness of having the mangled name to > correspond to looking at the assembly easier and in some cases the > "pretty name" will be the same but the mangled name will be different > (C++ constructors/destructors for an example) so understanding which > is which is important even for humans.
I submitted the patch formally here: https://gcc.gnu.org/pipermail/gcc-patches/2026-May/717765.html Thanks, Andrea > > Thanks, > Andrea > > > > > -- > > Eric Botcazou > > > >
