This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug ipa/80728] IPA-reference suppresses compiler memory barrier
- From: "rguenth at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 15 May 2017 08:42:50 +0000
- Subject: [Bug ipa/80728] IPA-reference suppresses compiler memory barrier
- Auto-submitted: auto-generated
- References: <bug-80728-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80728
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hubicka at gcc dot gnu.org,
| |rguenth at gcc dot gnu.org
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
x/3 (x) @0x7f32cb27a170
Type: function definition analyzed
Visibility: prevailing_def_ironly
References: b/1 (read)
Referring:
Availability: local
First run: 0
Function flags: body local
Called by: f/4 (1.00 per call)
Calls:
so IPA references are only listing explicit references and referring/references
has no way to catch the "escape" site.
Honza?
Note that in other PRs we explicitely said that "locals" (which includes
static globals) need explicit clobbering. That is, automatic vars that
do not have their address taken are not considered accessible by a
"memory" clobber either.