I also suspect it's a bug in the C compiler. So this begs the question of how to correct this situation. But first a clarifying question: does this behavior occur because the C compiler (which has the suspected bug in it) is accessed at runtime or was the bug "hardcoded" into Perl during Perl's compilation by this C compiler?

If the behavior occurs only because the C compiler is accessed during runtime then it may be only a case of getting the latest C runtime compiler patch to correct this behavior.

If the behavior occurs because the C compiler had a bug during Perl's compilation then either Perl will have to be recompiled (with an updated C compiler, of course) or a new Perl installation of previously compiled-for-Linux code will have to be installed.