Michael Matz
unread,Dec 7, 2022, 10:19:09 AM12/7/22Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Jan Beulich, Carlos O'Donell, H.J. Lu, x86-64-abi
Hello,
On Wed, 7 Dec 2022, 'Jan Beulich' via X86-64 System V Application Binary Interface wrote:
> >> Remove MPX support since MPX has been deprecated:
> >>
> >>
https://gitlab.com/x86-psABIs/x86-64-ABI/-/merge_requests/39
> >>
> >
> > Commented in the MR. LGTM.
> >
> > I don't know if we have a method to preserve historical data, but if someone
> > wants it they can just get it out of git. In the context of keeping a tidy
> > and accurate psABI we should be updating it as frequently as required.
>
> I didn't think anything that was implemented and used in practice
> could ever be removed from a psABI (or gABI, for that matter), and
> to me "deprecated" also only means exactly that.
Normally I would agree with you. In this case, MPX, I think removing it
from the psABI is okay and the right thing to do. And while it indeed was
implemented, I think "used in practice" is overstating things :)
The upside of removal is (besides the obvious ease on maintaining the
psABI text) that if someone comes up with something similar-but-not-equal
to MPX in the future there's no precedent anymore in the psABI that might
constrain a good design.
(And yeah: an alternative would have been to introduce an "obsolete stuff"
section and move MPX there, but I think that would have been the worse
choice)
Ciao,
Michael.