Deutsch English Français Italiano |
<o83i3jt87evip2lv6nfcip1kii64f3ef2b@4ax.com> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: John Savard <quadibloc@servername.invalid> Newsgroups: comp.arch Subject: Re: Oops (Concertina II Going Around in Circles) Date: Mon, 06 May 2024 11:06:44 -0600 Organization: A noiseless patient Spider Lines: 25 Message-ID: <o83i3jt87evip2lv6nfcip1kii64f3ef2b@4ax.com> References: <kipj2j5be9kuv8rn770iq6neq2cvu3s5oi@4ax.com> <moae3jhjbcqarvfpkcorta8av7g896rm75@4ax.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Injection-Date: Mon, 06 May 2024 19:06:47 +0200 (CEST) Injection-Info: dont-email.me; posting-host="3084e56c93532a97ce5f3e35e97724c8"; logging-data="2830250"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/bv/by2eRNWyoNW6vZQZTORaTUm/K9Eos=" Cancel-Lock: sha1:GOJOlZe3lGMgkKv44N0zm46yDds= X-Newsreader: Forte Free Agent 3.3/32.846 Bytes: 2129 On Sun, 05 May 2024 00:57:44 -0600, John Savard <quadibloc@servername.invalid> wrote: >The final one is 1111 that allows 17-bit instructions, 48, 64, 80, and >96 bit instructions, and their arbitrary mixing. However, one thing I wanted to do was have the 48-bit and longer instructions also available outside of the variable-length format. Previously, I had done this by having a second format of long instructions. I wanted to avoid that, this time. I came up with an idea. Just as 1111 _after_ the header in variable-length mode was used to indicate long instructions, for other modes, let 1111 after the header indicate each of two instruction slots in which three 18-bit units from variable-length are encapsulated. So a 48-bit instruction, taking up 64 bits, could be placed in any of the other modes. But because that code conflicts with the header, these things aren't first-class citizens! I tried freeing up 1110 as well, but that was clearly not going to work acceptably. So I took other measures that only partly addressed that issue but consumed far less opcode space. John Savard