<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>I already said this, but more concretely, I propose M3CG_Ops additions:<br><br>set_target_name(name: TEXT);<br>TYPE Endian = { Little, Big }; (* or Endian_t or Endian_e *)<br>set_endian(endian: Endian);<br>set_wordsize(wordsize: INTEGER); (* currently always 32 or 64 *)<br><br><br>I MIGHT have use of these in m3back/M3C.<br>I'm not sure yet.<br><br><br>target_name implies endian and wordsize and more, but it a kind of vague thing.<br>It also implies win32 vs. Posix, which M3C probably won't need.<br>It also implies jmpbuf size, which might be useful, or maybe we remove that "the other way".<br>You know -- I want to eventually remove target knowledge from m3front, and have none in M3C either.<br><br><br> - Jay<br> </div></body>
</html>