https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113867
--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> --- Created attachment 57398 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57398&action=edit Patch - handling the libgomp issue Possible patch - lightly tested. This fixes the issue in libgomp. While always correct and possibly avoiding other corner cases (if there are any), an alternative approach is to not create those 'struct: s [len: 1]' + 'alloc:s2.p [len: 0]'. RFC: - Is there a reason why we want to have the struct in such a case? (GCC <= 13 doesn't create this struct) - Do we want to have this libgomp change even when not generating the struct as extra safety net?
