Re: Bit swizzling

Hans-Peter Diettrich <>
Tue, 8 Sep 2020 01:45:41 +0200

          From comp.compilers

Related articles
[2 earlier articles]
Re: Bit Swizzling (John Levine) (2020-09-05)
Re: Bit swizzling (Kaz Kylheku) (2020-09-05)
Re: Bit swizzling ( (2020-09-06)
Re: Bit Swizzling (Chris) (2020-09-06)
Re: Bit swizzling (Martin Ward) (2020-09-07)
Re: Bit swizzling (Rick C. Hodgin) (2020-09-07)
Re: Bit swizzling (Hans-Peter Diettrich) (2020-09-08)
Re: Bit swizzling (Tom Crick) (2020-09-08)
Re: Bit swizzling (gah4) (2020-09-10)
Re: Bit swizzling (Rick C. Hodgin) (2020-09-10)
| List of all articles for this month |

From: Hans-Peter Diettrich <>
Newsgroups: comp.compilers
Date: Tue, 8 Sep 2020 01:45:41 +0200
Organization: Compilers Central
References: 20-09-014 <> 20-09-021
Injection-Info:; posting-host=""; logging-data="50896"; mail-complaints-to=""
Keywords: optimize
Posted-Date: 07 Sep 2020 20:57:12 EDT
In-Reply-To: 20-09-021

Am 07.09.2020 um 16:55 schrieb Rick C. Hodgin:

> One such idea is writing to a port, and reading back from another port,
> where the external thing does the processing for you as a co-processor or
> custom ASIC.

In a more general approach you connect a ROM between the output and
input port, for any possible mapping of n-into-n bits. Nowadays a table
in flash memory is better applicable.


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.