https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105523
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2022-11-23
Status|UNCONFIRMED |NEW
--- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to LIU Hao from comment #6)
> Apparently GCC thinks we are dereferencing `0x30` which is a dangling
> pointer however that is exactly what we want to do, so GCC shouldn't have
> warned in this case.
That inline-asm is not correct and GCC does not understand segments if you
don't use named address space feature.
The original issue is confirmed.
