Jeffrey A Law
Thu Jun 25 10:54:00 GMT 1998
In message < 199806251749.KAA03423@smtp.earthlink.net >you write:
> Jeffrey> I think we need to save/restore the current alias set #
> Jeffrey> as we change function contexts so that the current alias
> Jeffrey> set # isn't scrogged when we compile a nested function.
> Jeffrey> Even if this isn't an issue right now we need to go ahead
> Jeffrey> and save/restore the set #. It's simple to do, so I
> Jeffrey> don't think you need to resubmit after making this
> Jeffrey> change.
> I don't quite get this. With my patch, the C front-end assigns alias
> sets to types lazily, as it creates MEMs who need alias sets. It
> doesn't make sense to have different types in the same alias set, so I
> don't see why we'd ever want to restore the alias set counter to a
> previous value. It should monotonically increase, I think.
Do they monotonically increase through a function or through an
entire compilation unit.
If the former, then we need to save/restore as we change function
contexts. If the latter, then we do not need to save/restore it.
More information about the Gcc-patches