GDB is supposed to skip eacho sequence (__asm__ block) in response
to a "next", but it may have had its behavior changed from when i
originally wrote this. It seems to take multiple next's to get to a
different __asm__ block now, so it seems to be broken.
It may be a difference in GCC's debuginfo output or GDB just got smarter.
I might be wrong, but I don't remember us changing anything in this
area. "next/step" behavior is really determined by the line info
generated by the compiler. If the compiler was changed from not
generated a line entry for the __asm__ blocks, and now does, then
it'll change GDB's behavior. If next/step behavior testing is
important to the testcase, then it would seem to make sense to
convert the testcase to using an assembly file instead.