You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using gcc mips, gcc mips64, or gcc loongarch64, many debug labels beginning with $LVL$LBE and $LBB are present in the assembly output. This makes the output very hard to read. The problem is pronounced when using optimization flags as they add a lot more of these labels.
As a workaround, the labels can be disabled by manually passing the -g0 flag, but that also prevents the line colouring from working.
Steps to reproduce
Visit gcc.godbolt.org
Select any of the mips gcc, mips64 gcc or loongarch64 gcc compilers
Write a function with a few statements
Add the -O flag to compiler options
Look in the assembly output
Expected behavior
I expect the output to match the behavior of the other compilers, where these labels are hidden.
Describe the bug
When using gcc mips, gcc mips64, or gcc loongarch64, many debug labels beginning with
$LVL
$LBE
and$LBB
are present in the assembly output. This makes the output very hard to read. The problem is pronounced when using optimization flags as they add a lot more of these labels.As a workaround, the labels can be disabled by manually passing the
-g0
flag, but that also prevents the line colouring from working.Steps to reproduce
-O
flag to compiler optionsExpected behavior
I expect the output to match the behavior of the other compilers, where these labels are hidden.
Reproduction link
https://gcc.godbolt.org/z/qvr915Ysz
Screenshots
Operating System
No response
Browser version
No response
The text was updated successfully, but these errors were encountered: