> if you look at the type-translation-tables, there
> is kind of a "hack" to support the Plan 9 compiler
> as well. The idiom of making a pointer struct-array
> was circumvented to avoid doing that.
I didn't understand what you meant by “make the changes in the
arch-code-lookup-tables”, I thought
On Tue, 7 Jun 2016 16:42:13 +0200
Qentin Rameau wrote:
Hey Quentin,
> Why would I have?
> scc is the driver, it's not bound to cc1 or cc2.
if you look at the type-translation-tables, there
is kind of a "hack" to support the Plan 9 compiler
as well. The idiom of making a
> Hey Quentin,
hi
> I was already wondering. If you had applied that change, you would've
> also had to make the changes in the arch-code-lookup-tables.
Why would I have?
scc is the driver, it's not bound to cc1 or cc2.
On Tue, 7 Jun 2016 15:22:13 +0200 (CEST)
g...@suckless.org wrote:
Hey Quentin,
> Revert "[driver] use pointers in tools lookup table"
>
> This reverts commit 86e6d58d2e1059bb493df922bc89a1cc2b92ee83.
>
> This was a leftover from a test I forgot to drop before pushing.
>