t
make install
-Original Message-
From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org]
On Behalf Of grischka
Sent: vendredi 13 octobre 2017 20:37
To: tinycc-devel@nongnu.org
Subject: Re: [Tinycc-devel] plans to 0.9.27
Christian Jullien wrote:
> But worse, I'
--
From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org]
On Behalf Of grischka
Sent: jeudi 12 octobre 2017 09:32
To: tinycc-devel@nongnu.org
Subject: Re: [Tinycc-devel] plans to 0.9.27
Christian Jullien wrote:
Chris,
This is precisely why I wrote win32/Makefile which, with
n. Can you please check and tell me if I'm wrong or
the way I can run "make test" using W/tcc?
C.
-Original Message-
From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org]
On Behalf Of grischka
Sent: jeudi 12 octobre 2017 09:32
To: tinycc-devel@non
gt;> But this is a very huge task to make it work. Until then, I'll continue to
>> use my Makefile on Cygwin which is close to my ideal.
>>
>> Christian
>>
>>
>> -Original Message-
>> From: Tinycc-devel
>> [mailto:tinycc-devel-bounces+eligis=ora
can generate both -m32/-m64 native Windows code outside cygwin
environment).
C.
Le : 12 octobre 2017 à 10:02 (GMT +02:00)
De : "grischka" <gris...@gmx.de>
À : "tinycc-devel@nongnu.org" <tinycc-devel@nongnu.org>
Objet : Re: [Tinycc-devel] plans to 0.9.27
Christian J
nycc-devel@nongnu.org
Subject: Re: [Tinycc-devel] plans to 0.9.27
I just confirmed that restoring the "build windows tcc with cygwin"
win32/Makefile still works.
Since there is no posix cygwin build of tcc available, I suggest not breaking
the cygwin build until there is an actual po
nycc-devel] plans to 0.9.27
I just confirmed that restoring the "build windows tcc with cygwin"
win32/Makefile still works.
Since there is no posix cygwin build of tcc available, I suggest not breaking
the cygwin build until there is an actual posix/cygwin tcc build supported.
After
I just confirmed that restoring the "build
windows tcc with cygwin" win32/Makefile still
works.
Since there is no posix cygwin build of tcc
available, I suggest not breaking the cygwin
build until there is an actual posix/cygwin
tcc build supported.
After the 0.9.27 official release, I look
forw
I was able to 'make' and 'make test' with
the original win32/Makefile. I got home and
tried the "new" version building with cygwin
and now it doesn't pass tests because it says
-run is not valid for a cross compiler.
I think this is a bug since tcc does not
have a posix version for cygwin so whi
Indeed fantastic.
Just tested on Alpine linux, and tcc now builds tmux, htop, st (x terminal),
freetype2 (but ft2 doesn't link), an order of magnitude faster than gcc. And
gcc on Alpine is already faster than elsewhere, maybe because of s/glibc/musl/.
The resulting binaries seem to work fine, tho
grischka wrote:
|grischka wrote:
...
|Moreover, there is
|* a patch to tccelf.c to avoid DT_TEXTREL unless really required
|* a nifty one in tccasm.c to avoid the 'p3' forward label from
| alloca86_64.S being put into dynsym with a relocation (huh?)
|* and the (sig)set variable in tcctest
grischka wrote:
avih wrote:
Two things:
1. Will the version be 0.9.27 or 0.9.28?
0.9.27.
2. On windows in msys2 mingw 64 environment with gcc 7.2.0, (building
tcc 64 for windows with mingw gcc 64) the build completes but some
tests fail (see below).
Now, I fixed that, plus the ARM signed
avih wrote:
Two things:
1. Will the version be 0.9.27 or 0.9.28?
0.9.27.
2. On windows in msys2 mingw 64 environment with gcc 7.2.0, (building tcc 64
for windows with mingw gcc 64) the build completes but some tests fail (see
below).
Works for me with gcc 5.3 and earlier but does not wit
2017 20:51
To: Christian Jullien; tinycc-devel@nongnu.org
Subject: Re: [Tinycc-devel] plans to 0.9.27 (was 0.9.28)
Christian Jullien wrote:
> While mod after you last commit works great on Windows 32/64 Rpi arm
>
> It has one issue on Aarch64 (yet I don't know if it is related to
Christian Jullien wrote:
While mod after you last commit works great on
Windows 32/64
Rpi arm
It has one issue on Aarch64 (yet I don't know if it is related to your last
commit or not):
Hm. It might have to do with unsigned-ness of chars on arm. If so
it is a bug in the test and the change b
15 matches
Mail list logo
