Hi Peter,
gcc -c -O1 -ggdb -masm=intel -Wa,-acdhlgn=gfp_library.lst -Wa,-- listing-lhs-width=4,--listing-rhs-width=132 -o gfp_library.o gfp_library.c
In the future if you have other bugs like this to report, please could you capture the compiler's assembler output and provide that as the test file, rather than the C source ? The reason being that this eliminates one step in the process and it means that I do not need to have exactly the same version of gcc installed on my machine. Also - it really helps if you can file a bug report with the binutils bugzilla system: https://sourceware.org/bugzilla/enter_bug.cgi?product=binutils This lets us track the bug and any discussion about it. Plus we can put comments in the code referring to the bug's PR number and even create new tests that refer back to the bug report as well. As it happens however I am able to reproduce the problem locally, and the first thing that occurs to be is to wonder why you are capturing an assembler listing ? And given that it is needed, why do you need a limit on the width of the source code in the listing ? The problem is obviously in the listing code, which is old and crufty. I am taking a look however and I may be able to find a solution. Cheers Nick
