https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90859
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-06-20
Ever confirmed|0 |1
--- Comment #2 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Experimenting on x86_64-pc-linux-gnu with '-m32', this depends on the data type
used for 'array_so'. If I change 'uint32_t' to 'unsigned int', I see the same
strange behavior. If however I change it to 'unsigned long', the issue goes
away, as it does for 'unsigned short', for example. The code inside the region
is the same (aside from some type casting); in particular there aren't any
'array' references.
Per 'gcc-testresults' received so far, the issue does not appear (thus, 'FAIL'
for this 'scan-tree-dump') on powerpc-ibm-aix7.2.0.0, aarch64-suse-linux-gnu
with '-mabi=ilp32' (manually confirmed), s390x-ibm-linux-gnu with '-m31',
i686-apple-darwin9, powerpc-apple-darwin9, x86_64-apple-darwin16,
x86_64-apple-darwin17.
