"Combine text sections" gets confused by ARM constant pools

[LagoLunatic]

Commit: Seems to have been introduced on eaba239, still happens on latest commit

When "Combine text sections" is enabled, some objects have most of their functions interpreted as being data instead:

This doesn't seem to happen to the first function in the object:

It seems to think that the first function's constant pool continues and covers every other function in the TU.

Not all objects are affected by this issue. Some have the opposite issue, where it interprets both constant pools and code as being code:

The difference between these two types of issue appears to be the first function in the TU - if it has a constant pool, all the functions after it will be interpreted as constant pools. If it doesn't have a constant pool, all the constant pools after it will be interpreted as code.

Here are both objects (enemy100 has the first issue, enemy300 has the second):
armcombine.zip

Neither issue happens when text sections aren't combined.