https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105863
--- Comment #11 from Joseph S. Myers <jsm28 at gcc dot gnu.org> --- It makes the changes more complicated (everything that handles CONSTRUCTORs, whether to output them to assembly or to extract values for optimization etc., needs to handle the new tree), but yes, having a new tree would allow more efficient handling of additional cases that wouldn't be so efficient with STRING_CST.
