https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103223
--- Comment #8 from hubicka at kam dot mff.cuni.cz --- > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103223 > > --- Comment #5 from Martin Sebor <msebor at gcc dot gnu.org> --- > (In reply to Martin Jambor from comment #4) > > (In reply to Jan Hubicka from comment #0) > ... > > > Martin, I wonder if if you would be OK with simply dropping the access > > > when > > > function signature changes (which I can prepare patch for) or do you want > > > to > > > dive into updating it? > > > > I would be OK with it but I don't think people who invested the energy > > into these new security warnings would. > > I replied earlier on gcc-patches: I've always intended the access attribute to > eventually benefit optimization so please feel free (and encouraged :) to use > it > for that purpose. The idea behind it was not just to catch bugs but also to > enable optimizations based on the expectation that those bugs will have been > fixed. (This has to be done carefully since the attribute is also implicitly > added in contexts where relying on it wouldn't correct for optimization; the > attirbute API makes it possible to distinguish these cases.) Is there some summary of what information the access attribute holds in addition to what we have in fnspec (which is used for the optimization)? > > By dropping the attribute in IPA passes we would not only give up on detecting > the bugs the IPA transformations expose but also on the optimization > opportunities they might open up. Yep, I hope it is not too hard to write code updating the attribute after transformation. We drop the attribute only when we actually do some change on function parameters. ipa-modref solves similar problem of updating the modref summaries after changes. What I do is to simply compute map translating old parameter indexes to new via: clone_info *info = clone_info::get (node); FOR_EACH_VEC_SAFE_ELT (info->param_adjustments->m_adj_params, i, p) { int idx = info->param_adjustments->get_original_index (i); if (idx > (int)max) max = idx; } auto_vec <int, 32> map; map.reserve (max + 1); for (i = 0; i <= max; i++) map.quick_push (-1); FOR_EACH_VEC_SAFE_ELT (info->param_adjustments->m_adj_params, i, p) { int idx = info->param_adjustments->get_original_index (i); if (idx >= 0) map[idx] = i; } and then I simply rewrite old parameter indexes to new and drop parts of info that uses parameters that was either removed or replaced by scalars/components. Similarly we can do for access attribute.