[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Tinycc-devel] tcc(1) from current [mob] doesn't recognize "const" a
From: |
Steffen Nurpmeso |
Subject: |
Re: [Tinycc-devel] tcc(1) from current [mob] doesn't recognize "const" attribute suffix |
Date: |
Mon, 28 Mar 2016 14:36:13 +0200 |
User-agent: |
s-nail v14.8.8-163-ga22a94e |
Hello!
Michael Matz <address@hidden> wrote:
|On Thu, 24 Mar 2016, Steffen Nurpmeso wrote:
|>|Can't reproduce, please provide a testcase.
|>
|> I still can. I'll attach a heavily vaporised variant of the
|> source in question, just run "make build" and it should happen --
|Thanks for the testcase. The problem is ideosyncratic use of volatile:
|
| char c;
| char volatile vc;
| vc = c;
..I was too lazy to boil it down in an intelligent way..
|Here volatile doesn't make much sense, but tripped TCCs assertions.
|Fixed in mob. Thanks again for the report.
Fantastic, i can use tcc(1) again! That truly is the RAD that
i like, screen plus mksh plus vim plus tcc!
It seems [mob] has become smart enough to realise that the
primitive test program that is used to check wether a compiler
flag works or not doesn't need boundary checks. Well. I disabled
the -b flag.
tcc: error: undefined symbol '__bounds_start'
I've also recognized inconsistent behaviour regarding options:
address@hidden tmp]$ tcc -go zt t.c
zt:1: error: unrecognized character \x7f
address@hidden tmp]$ tcc -dg -o zt t.c
tcc: error: invalid option -- '-dg'
Thanks a lot for the quick fixes! Ciao!!
--steffen