<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Daniel,</div><div><br></div><div>LONGINT and INTEGER are scalar types with no relation except one's values are subset of another. References to them are strongly typed in Modula-3 - meaning types are semantically different - but their representation is same as ADDRESS. In single address space you have all memory location addressable by same pointer type - ADDRESS. They can differ in alignment, depending on implementation decisions, but that is something else. Implementation-wise, REF LONGINT and REF INTEGER are same type. Implied semantical informationis used where it is needed and it is not worry of language user unless she/he does something related to language environments other than Modula-3. Think RPC, OpenCL (GPU), ...</div><div><br></div><div>On LINUXLIBC6 ADDRESS type is 32bit, 4byte. On AMD64_DARWIN it's 64bit, 8byte. Most 64bit platforms today are limited in number of address lines from CPU to memory, IIRC Alpha had 48bit physical memory interface. I am sure it is limited to some number smaller than 64 on every 64bit platform today. But - that does not mean (Modula-3) language implementor will make PHYSADDRESS pointer type 6 bytes long. You probably can find such types in some experimental languages you are interested in. Good luck there, for/but I am not :). </div><div><br></div><div><div>Unless my English-foreign is mismatched more than I think to your English-foreign, we are almost orthogonal in this discussion for some time. I checked, I am still writing to m3devel. Are you? :)</div><div><br></div><div>dd</div><div><br><div><div>On Apr 26, 2012, at 6:58 PM, Daniel Alejandro Benavides D. wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><table cellspacing="0" cellpadding="0" border="0"><tbody><tr><td valign="top" style="font: inherit;">Hi all:<br>In that sense, it's neither Physical or logical but process communications are both (so hat's why its called Inter-process), but conceptually, you can speak of that if that's what you mean.<br>In one of such architectures (as a Bus-oriented architecture micro-processor) there are Logical Address (INTEGER), as the direction of a physical processor bus ID, (where there is a one to one mapping LBID to PBID) or a System Bus ID (ADDRESS), which identifies the location of a kernel function.<br>Thank your LONGINT is easy just to say LONGINT->LONGADDRESS, because you would want such a type of LBID address and function location, wouldn't you? And then the location itself is and expressed by REF LONGINT<:REF INTEGER<br>and LONGADDRESS<:ADDRESS so that the same function maps <br>LONGINT ->ADDRESS<br>Modula-3 type hierarchy does say
that, doesn't it? This is because it is contra variant type hierarchy.<br>Thanks in advance<br><br><br>--- El <b>mié, 25/4/12, Dragiša Durić <i><<a href="mailto:dragisha@m3w.org">dragisha@m3w.org</a>></i></b> escribió:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>De: Dragiša Durić <<a href="mailto:dragisha@m3w.org">dragisha@m3w.org</a>><br>Asunto: Re: [M3devel] LONGADDRESS [was: Re: Downsides of Modula-3 ?]<br>Para: "Daniel Alejandro Benavides D." <<a href="mailto:dabenavidesd@yahoo.es">dabenavidesd@yahoo.es</a>><br>CC: "felipe valdez" <<a href="mailto:dataf4l@gmail.com">dataf4l@gmail.com</a>>, <a href="mailto:m3devel@elegosoft.com">m3devel@elegosoft.com</a><br>Fecha: miércoles, 25 de abril, 2012 16:37<br><br><div id="yiv1274862872"><div>Single "execution space" can span over various architectures in few ways. Examples - RPC and GPU.<div><div><br></div><div>RPC is nothing new and it does not presume multi architecture for single object file. Nor it presumes single address space for various components/processes. There is cross-process boundary where
conversions (data marshaling/unmarshalling) happen. <div><br></div><div>On the other hand, GPU programming… No cross-process boundary in RPC style, it almost looks like it is single executable - but it is not "multiple CPU architecture per single object". Nor does it include single address space for various object components included.</div><div><br></div><div>GPU is an excellent example of what you are, very obliquely, hinting at. But - it is not single object file for multiple architectures for single address space. </div><div><br></div><div>It is probably good idea for you to look at GPU's today to see what is realistic in multi-architecture object generation/application.</div><div><div><br><div><div>On Apr 25, 2012, at 9:24 PM, Daniel Alejandro Benavides D. wrote:</div><br class="yiv1274862872Apple-interchange-newline"><blockquote type="cite"><table border="0" cellpadding="0" cellspacing="0"><tbody><tr><td style="font-family: inherit;
font-style: inherit; font-variant: inherit; font-weight: inherit; font-size: inherit; line-height: inherit; font-size-adjust: inherit; font-stretch: inherit;" valign="top">Hi all:<br>Such as a module generating code, for sending both LONGINTs and LONGADDRESSes through networks of wide processing units MCU (e.g array processors)?<br><a rel="nofollow" target="_blank" href="http://books.google.com.co/books?id=oM4EAQAAIAAJ&q=%22Address+register+2%22#search_anchor">http://books.google.com.co/books?id=oM4EAQAAIAAJ&q=%22Address+register+2%22#search_anchor</a><br><br><a href="http://books.google.com.co/books?id=oM4EAQAAIAAJ&q=74ACT8847#search_anchor">http://books.google.com.co/books?id=oM4EAQAAIAAJ&q=74ACT8847#search_anchor</a><br><br>I guess I should tell you one, but there are too many to count examples, in any case you would want to be truly multi platform and cross-porting easier in general, rather than based in one base case, though Modula was too good to make such things difficult in any case. If it serves to know
multitasking of DEC has been emulated through the AMD Bulldozer microarchitecture with Array/Vector processor, etc. But it still needs more cooperation (or at least using shared standards) on the industry to return to those
good days.<br><br>Thanks in advance <br><br>--- El <b>mié, 25/4/12, felipe valdez <i><dataf4l@gmail.com></i></b> escribió:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>De: felipe valdez <dataf4l@gmail.com><br>Asunto: Re: [M3devel] LONGADDRESS [was: Re: Downsides of Modula-3 ?]<br>Para: "Dragiša Durić" <dragisha@m3w.org><br>CC: "Daniel Alejandro Benavides D." <dabenavidesd@yahoo.es>, m3devel@elegosoft.com<br>Fecha: miércoles, 25 de abril, 2012 11:08<br><br><div id="yiv1274862872"><div class="yiv1274862872gmail_extra">that is quite a response.</div><div class="yiv1274862872gmail_extra"><br><br><div class="yiv1274862872gmail_quote">On Wed, Apr 25, 2012 at 8:08 AM, Dragiša Durić <span dir="ltr"><<a rel="nofollow">dragisha@m3w.org</a>></span> wrote:<br>
<blockquote class="yiv1274862872gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div style="">As my first hands-on CPU was 6502, I think I remember a lot.<div><br></div><div>ADDRESS is pointer size, and even C world spins around one pointer size per architecture. Of course there are various architectures, with their various specifics. Not only pointer size, of course. </div>
<div><br></div><div>What use would be to have two pointer sizes in single project? Do you expect one thread of your program to run on one CPU, second thread on another, different CPU?</div><div><br></div><div><div><div><div>
On Apr 24, 2012, at 4:42 PM, Daniel Alejandro Benavides D. wrote:</div><br><blockquote type="cite"><span style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; font-size: medium;">Hi all:<br>
All the contrary Dragisha, do you remember the Micro's era 6809, 4004, etc, so then it became gradually 68000, 8088 - 80186, etc.<br>So we can see in ARM versions, but now, probably in AMD64, that they are planning the next step, as were the same histories for those days.<br>
We could use it like for porting 32 bit backend to 64 bit painfully less stressful, I mean, even the OS/400 has this feature of 128 pointers to allow updating architecture, without language change.<br><br>So I'd guess is rather cross-portability, upwards and that's it. Of course this would require more TYPE declarations and VAR as well (LADR, LVAR), but could be less painful for the ones who want to port to that.<br>
It must be done carefully aggressively because this is a changing world, what can I say? <br>Thanks in advance</span></blockquote></div><br></div></div></div></blockquote></div><br><br clear="all"><br>-- <br><div>312-444-2124<div>
Skype: f3l.headhunter</div><div>Casa: 8043901</div></div><div><br></div><br>
</div>
</div></blockquote></td></tr></tbody></table></blockquote></div><br></div></div></div></div></div></div></blockquote></td></tr></tbody></table></blockquote></div><br></div></div></body></html>