https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105523
Ahmad Fatoum <ahmad at a3f dot at> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ahmad at a3f dot at
--- Comment #14 from Ahmad Fatoum <ahmad at a3f dot at> ---
Does param=min-pagesize=0 solely influence warnings or could it now or in the
future affect code generation/optimization?
I ask because barebox (https://barebox.org) also has this problem as on i.MX8,
where it calls into ROM code, which starts at address 0. After that's done, it
maps the NULL page there and normal accesses are unexpected. So if it's just
about the warning, I'd prefer hiding pointer value via a compiler barrier where
appliable instead of disabling the warning altogether.
