<div dir="ltr">You can propose it on that mailing list and consensus can form. You can also use a vendor specific emachine field by using a name like EM_LLVM_FOO. LLVM has extensions that are not agreed on anywhere else as well like partitions. For such extensions you merely need to reach consensus on llvm-dev (or the new decision process if that's been rolled out)</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 29, 2020 at 12:05 PM Fangrui Song via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 2020-01-29, connor horman via llvm-dev wrote:<br>
>Hello, I’m working on porting llvm to build for 65816, and I wanted to use<br>
>a value of e_machine for this. I was wondering if there is a process for<br>
>getting a value reserved. I’ve seen some information but its from many<br>
>years ago, and seems to be well out of date? Just wanted to ask people who<br>
>would likely know.<br>
<br>
>_______________________________________________<br>
>LLVM Developers mailing list<br>
><a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
><a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
<br>
The official ELF specification is hosted at<br>
<a href="http://www.sco.com/developers/gabi/latest/contents.html" rel="noreferrer" target="_blank">http://www.sco.com/developers/gabi/latest/contents.html</a><br>
<br>
After this post<br>
<a href="https://groups.google.com/forum/#!msg/generic-abi/IakWYdGABjQ/7zTiAVveBAAJ" rel="noreferrer" target="_blank">https://groups.google.com/forum/#!msg/generic-abi/IakWYdGABjQ/7zTiAVveBAAJ</a><br>
there is no more posts from them.<br>
<br>
In 2017, there was a post <br>
Recent e_machine assignments from Xinuos<br>
<a href="https://groups.google.com/forum/#!searchin/generic-abi/EM_%7Csort:date/generic-abi/cmq1LFFpWqU/plTYhw8kBwAJ" rel="noreferrer" target="_blank">https://groups.google.com/forum/#!searchin/generic-abi/EM_|sort:date/generic-abi/cmq1LFFpWqU/plTYhw8kBwAJ</a><br>
<br>
In 2018, a HermitCore developer attempted to ask <a href="mailto:registry@sco.com" target="_blank">registry@sco.com</a> but<br>
got no response.<br>
<a href="https://groups.google.com/forum/#!searchin/generic-abi/Fwd$3A$20Requesting$20an$20ELFOSABI$20constant$20for$20HermitCore%7Csort:date/generic-abi/vWu-rwjqi6c/e9JKzu0hBwAJ" rel="noreferrer" target="_blank">https://groups.google.com/forum/#!searchin/generic-abi/Fwd$3A$20Requesting$20an$20ELFOSABI$20constant$20for$20HermitCore%7Csort:date/generic-abi/vWu-rwjqi6c/e9JKzu0hBwAJ</a><br>
(I tried contacting them in 2019 to update<br>
<a href="http://www.sco.com/developers/gabi/latest/contents.html" rel="noreferrer" target="_blank">http://www.sco.com/developers/gabi/latest/contents.html</a> but there has<br>
been no response.)<br>
<br>
So the official ELF specification is probably in an unmaintained status.<br>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank">llvm-dev@lists.llvm.org</a><br>
<a href="https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer" target="_blank">https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</blockquote></div>