Re: mes wip-arm state

[Danny Milosavljevic]

Hi Janneke,

On Mon, 01 Jun 2020 08:33:30 +0200
Jan Nieuwenhuizen <janneke@gnu.org> wrote:

> I checked and I don't believe they do [force usage of signed char].

That's too bad because mescc ARM uses signed char (I haven't changed it, so it
should interpret "char" as signed char like it always did).

>How about just adding 'signed' to those tests above?
>We're really testing if sign extension works -- testing
> for signdness of char could/should be another test.  WDYT?

I agree.

> As we cannot rewrite master, I'd like to check if we didn't break
> anything for mes-x86 :-)

Sure.

> We can also make tcc work before merging, but we could also start a new
> wip-tcc / wip-arm-tcc later if the need arises.  Whatever works for you!

I'd definitely have the current state marked and stored somewhere--at least
tagged or something.

If it's not too much work, let's merge it into master.  I think I haven't
changed the compiler frontend much (or at all), so the risk of affecting x86
should be minimal.

If the changeset would touch something it shouldn't, let's stop merging then.

(The syscall stuff was technically changed--but only minimally by splitting
it into two source files so I don't have to carry errno everywhere.  Effect
for callers of _syscall* should be unchanged)

Let's definitely test it on x86, though :)

> As you propbably have seen, in the bootstrap we use a forked tcc:
> somewhat older (0.9.27), patched.
> 
>     https://gitlab.com/janneke/tinycc/-/tree/mes-0.21

I've checked it out now.

> ba1c47d * lotsa debug printing.

... and readded that for me.

Thanks!

How do I build tcc using mescc?

pgp3R4q2viQG7.pgp
Description: OpenPGP digital signature