Hello, On Thu, 3 Feb 2022, Richard Biener via Gcc-patches wrote:
> > > It indeed did occur to me as well, so as we're two now I tried to > > > see how it looks like. It does like the following (didn't bother to > > > replace all build_clobber calls but defaulted the parameter - there > > > are too many). > > > > Except for this part I like it (I wouldn't call ca. 25 calls too > > many). I often find optional arguments to be a long term maintenance > > burden when reading code. > > But I think in this case it makes clear that the remaining callers are > un-audited My pedantic answer to that would be that to make something clear you want to be explicit, and being explicit means writing something, not leaving something out, so you'd add another "CLOBBER_DONTKNOW" and use that for the unaudited calls. Pedantic, as I said :) But, of course, you built the shed, so paint it green, all right :) Ciao, Michael.
