https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89490
--- Comment #7 from Bernd Edlinger <bernd.edlinger at hotmail dot de> --- (In reply to Alan Modra from comment #6) > The zero bytes are added by the -fsection-anchors code. They used to align > the next object. Now, the number of zero bytes is wrong (in cases where we > used to have an unterminated string), *and* gcc's calculation of the offset > to the object within the section-anchor block is wrong. > > Misaligned strings will mean poorer performance on some targets. > Miscalculating the offset will result in wrong-code errors when it results > in too many objects being placed into a block. Well, I see, the alignment is not right, but even if the strings are near to each other, they will be moved to other segments, if the string constant was already used in another module. Are there cases where the string constants need to be near the section anchor, what is that and how does it look like in an assembly file?
