Re: [Tinycc-devel] plans to 0.9.27

2017-10-13 Thread Christian Jullien 
Grischka,

First, be sure I don't want to bother you for free. I KNOW for years how to
build and test Windows tcc (both 32/64) from Cygwin32 and Cygwin64 (it was
called win32/Makefile). It allowed anybody to easily test mod changes on
Windows.

My ONLY goal is to let other people to do the same.

So where are we?

Following you procedure I wrote a (long) script that works on Cygwin64 (but
not quite - see script at the end):

This script produces two Windows directories:
W64: which is a x64 version able to generate x64 (-m64 the default) and x86
code (-m32)
W32: which is a x86 version able to generate x86 (-m32 the default) BUT
fails with -m64:
/cygdrive/f/tinycc/W32$ ./tcc -m64 ../foo.c
tcc: error: could not run 'F:\tinycc\W32\x86_64-win32-tcc.exe'

Indeed:

/cygdrive/f/tinycc$ ls W* | more
W32:
doc
examples
include
lib
libtcc
libtcc.dll
tcc.exe

W64:
doc
examples
i386-win32-tcc.exe
include
lib
libtcc
libtcc.dll
tcc.exe

I'm quite OLD :o) but whether it was run on Cygwin32/64

$ cd win32; make all && make test

Was able to produce and test in one line all windows tcc material for
-m32/-m64

i386-win32-tcc.exe
tcc.exe
x86_64-win32-tcc.exe

IMHO, what is still missing is something (configure option, Makefile, script
or whatever) that works ROOTB (I mean very few simple commands) to produce
native Windows tcc that produce 32/64 code from Cygwin.

Don't hesitate to tell me I bother you too much and I'll definitely stop
this thread.

Here is what we must do to produce and test tcc on Windows with both 32/66
bit generated code but is not able to produce a working tcc -m64 version
from Cygwin32 (only from Cygwin64):


rm -r -f $PWD/X $PWD/W32 $PWD/W64

# build a cross-tcc using standard cygwin gcc and install in X:
make distclean
./configure --prefix=$PWD/X
make
make install
make distclean

# configure once for using that, anytime in future:
./configure --cc=$PWD/X/tcc --prefix=$PWD/W64

# build a native windows tcc, optionally with -m32/64, run full tests,
# and install as ready-to-use relocatable tree in W:

make
make cross-i386-win32
make test
make install

# make a i386 cross-compiler, too:
make distclean
./configure --prefix=$PWD/X
make
make cross-i386-win32
make install

# Then build the 32 bit tcc on win64 too:
make distclean
./configure --prefix=$PWD/W32 --cc=$PWD/X/i386-win32-tcc --cpu=i386
make clean
make
make test
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've also the impression that, after building W/tcc, make 
> test still uses Cygwin version.  Can you please check and tell me if 
> I'm wrong or the way I can run "make test" using W/tcc?

Some tests use the build CC (which normally is gcc) to create the reference
output.  Like .expect files but always fresh.

> Is there a way to detect that and run test two times, once with -m32, 
> once with -m64?

Not really.  However you can create a native 32 bit tcc and test that:

First make a i386 cross-compiler, too:

 ./configure --prefix=$PWD/X && make clean all cross-i386-win32 install

Then you can build the 32 bit tcc on win64 too:

 ./configure --prefix=$PWD/W32 --cc=$PWD/X/i386-win32-tcc --cpu=i386
 make clean all test install
 cd W32 && ./tcc -run examples/hello_win.c

-- gr

> 
> 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@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 only
> Cygwin+native Cygwin gcc, was able to bootstrap a native Windows tcc 
> Cygwin+for x86
> and x86_64 and check that all tests work.
>> Grischka disliked to have this Makefile and insisted to remove it. 
>> HIMO,
> we now lose the ability to very easily build native Windows tcc and 
> test it as there is no replacement atm.
>> I dislike the idea to install mingw on top of Cygwin just to produce 
>> native build while standard gcc is able to do that and works like a 
>> charm
> 
> ONLY for people who not are already TOO OLD to type some configure 
> options or TO TRY something NEW or DIFFERENT, eventually:
> 
> # build a cross-tcc using standard cygwin gcc and install in X:
> 
>  ./configure --prefix=$PWD/X
>  make
>  make install
>  make distclean
> 
> # configure once for using that, anytime in future:
> 
>  ./configure --cc=$PWD/X/tcc --prefix=$PWD/W
> 
> # build a native windows tcc, optionally

Re: [Tinycc-devel] plans to 0.9.27

2017-10-13 Thread grischka 

Christian Jullien wrote:

But worse, I've also the impression that, after building W/tcc, make test
still uses Cygwin version.  Can you please check and tell me if I'm wrong or
the way I can run "make test" using W/tcc?


Some tests use the build CC (which normally is gcc) to create
the reference output.  Like .expect files but always fresh.


Is there a way to detect that and run test two times, once with -m32, once
with -m64?


Not really.  However you can create a native 32 bit tcc and test that:

First make a i386 cross-compiler, too:

./configure --prefix=$PWD/X && make clean all cross-i386-win32 install

Then you can build the 32 bit tcc on win64 too:

./configure --prefix=$PWD/W32 --cc=$PWD/X/i386-win32-tcc --cpu=i386
make clean all test install
cd W32 && ./tcc -run examples/hello_win.c

-- gr



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@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 only

Cygwin+native Cygwin gcc, was able to bootstrap a native Windows tcc for x86
and x86_64 and check that all tests work.

Grischka disliked to have this Makefile and insisted to remove it. HIMO,

we now lose the ability to very easily build native Windows tcc and test it
as there is no replacement atm.
I dislike the idea to install mingw on top of Cygwin just to produce 
native build while standard gcc is able to do that and works like a 
charm


ONLY for people who not are already TOO OLD to type some configure options
or TO TRY something NEW or DIFFERENT, eventually:

# build a cross-tcc using standard cygwin gcc and install in X:

 ./configure --prefix=$PWD/X
 make
 make install
 make distclean

# configure once for using that, anytime in future:

 ./configure --cc=$PWD/X/tcc --prefix=$PWD/W

# build a native windows tcc, optionally with -m32/64, run full tests,
   and install as ready-to-use relocatable tree in W:

 make
 make cross-i386-win32  (cross-x86_64-win32 if on 32bits)
 make test
 make install

-- gr


Until we have a way to do  that, I'll continue to use my own

win32/Makefile (now private) copy.

Now, you can try to convince Grischka to restore it or ask him to add the

logic in main Makefile to produce Windows native tcc for x86/x86_64 with
just Cygwin+standard Cygwin gcc.

If we dream, we should have Canadian-cross compiler with just configure

--triplet; make. Where triplet is:

System types:
  --build=BUILD configure for building on BUILD [guessed]
  --host=HOST   cross-compile to build programs to run on HOST [BUILD]
  --target=TARGET   configure for building compilers for TARGET [HOST]

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=orange...@nongnu.org] On Behalf Of 
Chris Marshall

Sent: jeudi 12 octobre 2017 02:54
To: tinycc-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 posix/cygwin tcc build
supported.

After the 0.9.27 official release, I look forward to contributing

development of a native posix cygwin tcc.

--Chris

On 10/11/2017 19:14, Chris Marshall wrote:
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 while tcc is built with a cross compiler, if you are 
running tcc on windows (built with cygwin or otherwise) then you have 
a

*windows* tcc not a "cross-compiler".

But, the win32/Makefile worked like a charm and all tests pass 
with a simple build.


Cheers,
Chris


On 10/11/2017 12:20, grischka wrote:

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 char test, plus some other 
stuff.


Also, I removed the win32/Makefile (thanks to Christian's OK), and 
the VIP patch (it is just not how it should work), and the 
-iwithprefix option (what was the point without -iprefix).


Moreover, there is
* a patch to tccelf.c to avoid DT_TEXTREL unless really required
* a nifty one in tccasm.c

Re: [Tinycc-devel] plans to 0.9.27

2017-10-12 Thread Christian Jullien 
Hi Grischka,

Here are some news from OLD Christian :o)

First of all, with your explanations on how to build a native tcc, I'm very
close to be totally happy.

I'm building tcc using Cygwin64 with native gcc Cygwin x64:

/cygdrive/f/tinycc$ uname -a
CYGWIN_NT-10.0 coltrane 2.9.0(0.318/5/3) 2017-09-12 10:18 x86_64 Cygwin
/cygdrive/f/tinycc$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-cygwin/6.4.0/lto-wrapper.exe
Target: x86_64-pc-cygwin
Configured with:
/cygdrive/i/szsz/tmpp/gcc/gcc-6.4.0-1.x86_64/src/gcc-6.4.0/configure
--srcdir=/cygdrive/i/szsz/tmpp/gcc/gcc-6.4.0-1.x86_64/src/gcc-6.4.0
--prefix=/usr --exec-prefix=/usr --localstatedir=/var --sysconfdir=/etc
--docdir=/usr/share/doc/gcc --htmldir=/usr/share/doc/gcc/html -C
--build=x86_64-pc-cygwin --host=x86_64-pc-cygwin --target=x86_64-pc-cygwin
--without-libiconv-prefix --without-libintl-prefix --libexecdir=/usr/lib
--enable-shared --enable-shared-libgcc --enable-static
--enable-version-specific-runtime-libs --enable-bootstrap
--enable-__cxa_atexit --with-dwarf2 --with-tune=generic
--enable-languages=ada,c,c++,fortran,lto,objc,obj-c++ --enable-graphite
--enable-threads=posix --enable-libatomic --enable-libcilkrts
--enable-libgomp --enable-libitm --enable-libquadmath
--enable-libquadmath-support --enable-libssp --enable-libada
--disable-symvers --with-gnu-ld --with-gnu-as
--with-cloog-include=/usr/include/cloog-isl --without-libiconv-prefix
--without-libintl-prefix --with-system-zlib --enable-linker-build-id
--with-default-libstdcxx-abi=gcc4-compatible
Thread model: posix
gcc version 6.4.0 (GCC)

At the end, I get:
F:> dir *.exe
2017-10-13  06:16   294,400 i386-win32-tcc.exe
2017-10-13  06:1619,456 tcc.exe

F:>file *.exe
i386-win32-tcc.exe: PE32+ executable (console) x86-64 (stripped to external
PDB), for MS Windows
tcc.exe:PE32+ executable (console) x86-64 (stripped to external
PDB), for MS Windows

I wonder why i386-win32-tcc.exe is named like that while it's a native x64
bit executable?

The only real difference with my OLD Makefile is that "make test" only tests
default mode while mine was also testing -m32

Is there a way to detect that and run test two times, once with -m32, once
with -m64?

But worse, I've also the impression that, after building W/tcc, make test
still uses Cygwin version.  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@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 only
Cygwin+native Cygwin gcc, was able to bootstrap a native Windows tcc for x86
and x86_64 and check that all tests work.
> Grischka disliked to have this Makefile and insisted to remove it. HIMO,
we now lose the ability to very easily build native Windows tcc and test it
as there is no replacement atm.
> I dislike the idea to install mingw on top of Cygwin just to produce 
> native build while standard gcc is able to do that and works like a 
> charm

ONLY for people who not are already TOO OLD to type some configure options
or TO TRY something NEW or DIFFERENT, eventually:

# build a cross-tcc using standard cygwin gcc and install in X:

 ./configure --prefix=$PWD/X
 make
 make install
 make distclean

# configure once for using that, anytime in future:

 ./configure --cc=$PWD/X/tcc --prefix=$PWD/W

# build a native windows tcc, optionally with -m32/64, run full tests,
   and install as ready-to-use relocatable tree in W:

 make
 make cross-i386-win32  (cross-x86_64-win32 if on 32bits)
 make test
 make install

-- gr

> 
> Until we have a way to do  that, I'll continue to use my own
win32/Makefile (now private) copy.
> 
> Now, you can try to convince Grischka to restore it or ask him to add the
logic in main Makefile to produce Windows native tcc for x86/x86_64 with
just Cygwin+standard Cygwin gcc.
> 
> If we dream, we should have Canadian-cross compiler with just configure
--triplet; make. Where triplet is:
> 
> System types:
>   --build=BUILD configure for building on BUILD [guessed]
>   --host=HOST   cross-compile to build programs to run on HOST [BUILD]
>   --target=TARGET   configure for building compilers for TARGET [HOST]
> 
> 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=orange...@nongnu.org] On Behalf Of 
> Chris Marshall
> Sent: jeudi 12 octobre 2017 02:54
> To: tinycc

Re: [Tinycc-devel] plans to 0.9.27

2017-10-12 Thread Chris Marshall 
On Thu, Oct 12, 2017 at 3:31 AM, grischka  wrote:
> Christian Jullien wrote:
>>
>> Chris,
>>
>> This is precisely why I wrote win32/Makefile which, with only
>> Cygwin+native Cygwin gcc, was able to bootstrap a native Windows tcc for x86
>> and x86_64 and check that all tests work.
>> Grischka disliked to have this Makefile and insisted to remove it. HIMO,
>> we now lose the ability to very easily build native Windows tcc and test it
>> as there is no replacement atm.
>> I dislike the idea to install mingw on top of Cygwin just to produce
>> native build while standard gcc is able to do that and works like a charm
>
>
> ONLY for people who not are already TOO OLD to type some configure
> options or TO TRY something NEW or DIFFERENT, eventually:

In my case, I'm TOO NEW to tcc.  Thanks for the additional
documentation.  I was able to run full native window tests as
indicated.  Will this be added to README or win32/tcc-win32.txt
or both?

Thanks!
Chris

> # build a cross-tcc using standard cygwin gcc and install in X:
>
> ./configure --prefix=$PWD/X
> make
> make install
> make distclean
>
> # configure once for using that, anytime in future:
>
> ./configure --cc=$PWD/X/tcc --prefix=$PWD/W
>
> # build a native windows tcc, optionally with -m32/64, run full tests,
>   and install as ready-to-use relocatable tree in W:
>
> make
> make cross-i386-win32  (cross-x86_64-win32 if on 32bits)
> make test
> make install
>
> -- gr
>
>
>>
>> Until we have a way to do  that, I'll continue to use my own
>> win32/Makefile (now private) copy.
>>
>> Now, you can try to convince Grischka to restore it or ask him to add the
>> logic in main Makefile to produce Windows native tcc for x86/x86_64 with
>> just Cygwin+standard Cygwin gcc.
>>
>> If we dream, we should have Canadian-cross compiler with just configure
>> --triplet; make. Where triplet is:
>>
>> System types:
>>   --build=BUILD configure for building on BUILD [guessed]
>>   --host=HOST   cross-compile to build programs to run on HOST [BUILD]
>>   --target=TARGET   configure for building compilers for TARGET [HOST]
>>
>> 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=orange...@nongnu.org] On Behalf Of Chris
>> Marshall
>> Sent: jeudi 12 octobre 2017 02:54
>> To: tinycc-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 posix/cygwin tcc build
>> supported.
>>
>> After the 0.9.27 official release, I look forward to contributing
>> development of a native posix cygwin tcc.
>>
>> --Chris
>>
>> On 10/11/2017 19:14, Chris Marshall wrote:
>>>
>>> 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 while tcc is built with a cross compiler, if you are running tcc on
>>> windows (built with cygwin or otherwise) then you have a
>>> *windows* tcc not a "cross-compiler".
>>>
>>> But, the win32/Makefile worked like a charm and all tests pass with a
>>> simple build.
>>>
>>> Cheers,
>>> Chris
>>>
>>>
>>> On 10/11/2017 12:20, grischka wrote:
>>>>
>>>> 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 char test, plus some other stuff.
>>>>
>>>> Also, I

Re: [Tinycc-devel] plans to 0.9.27

2017-10-12 Thread Christian JULLIEN 
Grischka,

Thank you for your patience with me!
I hope to be not too OLD :o) to test exactly what you propose.
I will test it using Cygwin64 and the <b>default</b> gcc (for 
Cygwin64).
I'll be glad to inform you if it works as expected (i.e. if it produces a 
working tcc that 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 Jullien wrote:
> Chris,
> 
> This is precisely why I wrote win32/Makefile which, with only 
Cygwin+native Cygwin gcc, was able to bootstrap a native Windows tcc for x86 
and x86_64 and check that all tests work.
> Grischka disliked to have this Makefile and insisted to remove it. HIMO, 
we now lose the ability to very easily build native Windows tcc and test it as 
there is no replacement atm.
> I dislike the idea to install mingw on top of Cygwin just to produce 
native build while standard gcc is able to do that and works like a charm

ONLY for people who not are already TOO OLD to type some configure
options or TO TRY something NEW or DIFFERENT, eventually:

# build a cross-tcc using standard cygwin gcc and install in X:

 ./configure --prefix=$PWD/X
 make
 make install
 make distclean

# configure once for using that, anytime in future:

 ./configure --cc=$PWD/X/tcc --prefix=$PWD/W

# build a native windows tcc, optionally with -m32/64, run full tests,
   and install as ready-to-use relocatable tree in W:

 make
 make cross-i386-win32  (cross-x86_64-win32 if on 32bits)
 make test
 make install

-- gr

> 
> Until we have a way to do  that, I'll continue to use my own 
win32/Makefile (now private) copy.
> 
> Now, you can try to convince Grischka to restore it or ask him to add the 
logic in main Makefile to produce Windows native tcc for x86/x86_64 with just 
Cygwin+standard Cygwin gcc.
> 
> If we dream, we should have Canadian-cross compiler with just configure 
--triplet; make. Where triplet is:
> 
> System types:
>   --build=BUILD configure for building on BUILD [guessed]
>   --host=HOST   cross-compile to build programs to run on HOST [BUILD]
>   --target=TARGET   configure for building compilers for TARGET [HOST]
> 
> 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=orange...@nongnu.org] On Behalf Of Chris 
Marshall
> Sent: jeudi 12 octobre 2017 02:54
> To: tinycc-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 posix/cygwin tcc build 
supported.
> 
> After the 0.9.27 official release, I look forward to contributing 
development of a native posix cygwin tcc.
> 
> --Chris
> 
> On 10/11/2017 19:14, Chris Marshall wrote:
>> 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 while tcc is built with a cross compiler, if you are running 
>> tcc on windows (built with cygwin or otherwise) then you have a
>> *windows* tcc not a "cross-compiler".
>>
>> But, the win32/Makefile worked like a charm and all tests pass 
>> with a simple build.
>>
>> Cheers,
>> Chris
>>
>>
>> On 10/11/2017 12:20, grischka wrote:
>>> 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 char test, plus some other 
>>> stuff.
>>>
>>> Also, I removed the win32/Makefile (thanks to Christian's OK), and 
>>> the VIP patch (it is just not how it should work), and the 
>>> -iwithprefix option (what was the point without -iprefix).
>>>
>>> Moreover, there is
>&

Re: [Tinycc-devel] plans to 0.9.27

2017-10-12 Thread grischka 

Christian Jullien wrote:

Chris,

This is precisely why I wrote win32/Makefile which, with only Cygwin+native 
Cygwin gcc, was able to bootstrap a native Windows tcc for x86 and x86_64 and 
check that all tests work.
Grischka disliked to have this Makefile and insisted to remove it. HIMO, we now 
lose the ability to very easily build native Windows tcc and test it as there 
is no replacement atm.
I dislike the idea to install mingw on top of Cygwin just to produce native 
build while standard gcc is able to do that and works like a charm


ONLY for people who not are already TOO OLD to type some configure
options or TO TRY something NEW or DIFFERENT, eventually:

# build a cross-tcc using standard cygwin gcc and install in X:

./configure --prefix=$PWD/X
make
make install
make distclean

# configure once for using that, anytime in future:

./configure --cc=$PWD/X/tcc --prefix=$PWD/W

# build a native windows tcc, optionally with -m32/64, run full tests,
  and install as ready-to-use relocatable tree in W:

make
make cross-i386-win32  (cross-x86_64-win32 if on 32bits)
make test
make install

-- gr



Until we have a way to do  that, I'll continue to use my own win32/Makefile 
(now private) copy.

Now, you can try to convince Grischka to restore it or ask him to add the logic 
in main Makefile to produce Windows native tcc for x86/x86_64 with just 
Cygwin+standard Cygwin gcc.

If we dream, we should have Canadian-cross compiler with just configure 
--triplet; make. Where triplet is:

System types:
  --build=BUILD configure for building on BUILD [guessed]
  --host=HOST   cross-compile to build programs to run on HOST [BUILD]
  --target=TARGET   configure for building compilers for TARGET [HOST]

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=orange...@nongnu.org] On 
Behalf Of Chris Marshall
Sent: jeudi 12 octobre 2017 02:54
To: tinycc-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 posix/cygwin tcc build supported.

After the 0.9.27 official release, I look forward to contributing development 
of a native posix cygwin tcc.

--Chris

On 10/11/2017 19:14, Chris Marshall wrote:
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 while tcc is built with a cross compiler, if you are running 
tcc on windows (built with cygwin or otherwise) then you have a

*windows* tcc not a "cross-compiler".

But, the win32/Makefile worked like a charm and all tests pass 
with a simple build.


Cheers,
Chris


On 10/11/2017 12:20, grischka wrote:

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 char test, plus some other 
stuff.


Also, I removed the win32/Makefile (thanks to Christian's OK), and 
the VIP patch (it is just not how it should work), and the 
-iwithprefix option (what was the point without -iprefix).


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.c was made static to
  avoid some issue with inline asm that I didn't try to fix
* no diff -I option anymore to make tests work with busybox
* a patch to tccrun.c for better selinux support.

With these changes, tcc now seems to build and pass all tests cleanly 
on Alpine musl x86_64 standard-grsec and vanilla too, configured with

   ./configure --config-musl --with-selinux optionally also with
   --disable-static and/or --cc=tcc (once it was installed)

Patch is here:
http://repo.or.cz/tinycc.git/commitdiff/da8c62f75d893449e232944fc6256
6c020b4d010


You might realize that I bumped the 'master' branch too, which is 
meant to mean:

"This could be what we could release as 0,9,27, soon"

Say next week or so, last-minute-fixes/features notwithstanding.

Thanks,

-- gr

___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Re: [Tinycc-devel] plans to 0.9.27

2017-10-11 Thread Christian Jullien 
Chris,

This is precisely why I wrote win32/Makefile which, with only Cygwin+native 
Cygwin gcc, was able to bootstrap a native Windows tcc for x86 and x86_64 and 
check that all tests work.
Grischka disliked to have this Makefile and insisted to remove it. HIMO, we now 
lose the ability to very easily build native Windows tcc and test it as there 
is no replacement atm.
I dislike the idea to install mingw on top of Cygwin just to produce native 
build while standard gcc is able to do that and works like a charm

Until we have a way to do  that, I'll continue to use my own win32/Makefile 
(now private) copy.

Now, you can try to convince Grischka to restore it or ask him to add the logic 
in main Makefile to produce Windows native tcc for x86/x86_64 with just 
Cygwin+standard Cygwin gcc.

If we dream, we should have Canadian-cross compiler with just configure 
--triplet; make. Where triplet is:

System types:
  --build=BUILD configure for building on BUILD [guessed]
  --host=HOST   cross-compile to build programs to run on HOST [BUILD]
  --target=TARGET   configure for building compilers for TARGET [HOST]

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=orange...@nongnu.org] On 
Behalf Of Chris Marshall
Sent: jeudi 12 octobre 2017 02:54
To: tinycc-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 posix/cygwin tcc build supported.

After the 0.9.27 official release, I look forward to contributing development 
of a native posix cygwin tcc.

--Chris

On 10/11/2017 19:14, Chris Marshall wrote:
> 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 while tcc is built with a cross compiler, if you are running 
> tcc on windows (built with cygwin or otherwise) then you have a
> *windows* tcc not a "cross-compiler".
>
> But, the win32/Makefile worked like a charm and all tests pass 
> with a simple build.
>
> Cheers,
> Chris
>
>
> On 10/11/2017 12:20, grischka wrote:
>> 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 char test, plus some other 
>> stuff.
>>
>> Also, I removed the win32/Makefile (thanks to Christian's OK), and 
>> the VIP patch (it is just not how it should work), and the 
>> -iwithprefix option (what was the point without -iprefix).
>>
>> 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.c was made static to
>>   avoid some issue with inline asm that I didn't try to fix
>> * no diff -I option anymore to make tests work with busybox
>> * a patch to tccrun.c for better selinux support.
>>
>> With these changes, tcc now seems to build and pass all tests cleanly 
>> on Alpine musl x86_64 standard-grsec and vanilla too, configured with
>>./configure --config-musl --with-selinux optionally also with
>>--disable-static and/or --cc=tcc (once it was installed)
>>
>> Patch is here:
>> http://repo.or.cz/tinycc.git/commitdiff/da8c62f75d893449e232944fc6256
>> 6c020b4d010
>>
>>
>> You might realize that I bumped the 'master' branch too, which is 
>> meant to mean:
>> "This could be what we could release as 0,9,27, soon"
>>
>> Say next week or so, last-minute-fixes/features notwithstanding.
>>
>> Thanks,
>>
>> -- gr
>>
>> ___
>> Tinycc-devel mailing list
>> Tinycc-devel@nongnu.org
>> https://lists.nongnu.org/mailman/listinfo/tinycc-devel
>


___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel


___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Re: [Tinycc-devel] plans to 0.9.27

2017-10-11 Thread Chris Marshall 

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
forward to contributing development of
a native posix cygwin tcc.

--Chris

On 10/11/2017 19:14, Chris Marshall wrote:

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 while
tcc is built with a cross compiler, if you
are running tcc on windows (built with
cygwin or otherwise) then you have a
*windows* tcc not a "cross-compiler".

But, the win32/Makefile worked like a
charm and all tests pass with a simple
build.

Cheers,
Chris


On 10/11/2017 12:20, grischka wrote:

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 char test, plus some other
stuff.

Also, I removed the win32/Makefile (thanks to Christian's OK),
and the VIP patch (it is just not how it should work), and the
-iwithprefix option (what was the point without -iprefix).

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.c was made static to
  avoid some issue with inline asm that I didn't try to fix
* no diff -I option anymore to make tests work with busybox
* a patch to tccrun.c for better selinux support.

With these changes, tcc now seems to build and pass all tests
cleanly on Alpine musl x86_64 standard-grsec and vanilla too,
configured with
   ./configure --config-musl --with-selinux
optionally also with
   --disable-static and/or --cc=tcc (once it was installed)

Patch is here:
http://repo.or.cz/tinycc.git/commitdiff/da8c62f75d893449e232944fc62566c020b4d010 



You might realize that I bumped the 'master' branch too, which
is meant to mean:
    "This could be what we could release as 0,9,27, soon"

Say next week or so, last-minute-fixes/features notwithstanding.

Thanks,

-- gr

___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel





___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Re: [Tinycc-devel] plans to 0.9.27

2017-10-11 Thread Chris Marshall 

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 while
tcc is built with a cross compiler, if you
are running tcc on windows (built with
cygwin or otherwise) then you have a
*windows* tcc not a "cross-compiler".

But, the win32/Makefile worked like a
charm and all tests pass with a simple
build.

Cheers,
Chris


On 10/11/2017 12:20, grischka wrote:

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 char test, plus some other
stuff.

Also, I removed the win32/Makefile (thanks to Christian's OK),
and the VIP patch (it is just not how it should work), and the
-iwithprefix option (what was the point without -iprefix).

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.c was made static to
  avoid some issue with inline asm that I didn't try to fix
* no diff -I option anymore to make tests work with busybox
* a patch to tccrun.c for better selinux support.

With these changes, tcc now seems to build and pass all tests
cleanly on Alpine musl x86_64 standard-grsec and vanilla too,
configured with
   ./configure --config-musl --with-selinux
optionally also with
   --disable-static and/or --cc=tcc (once it was installed)

Patch is here:
http://repo.or.cz/tinycc.git/commitdiff/da8c62f75d893449e232944fc62566c020b4d010 



You might realize that I bumped the 'master' branch too, which
is meant to mean:
    "This could be what we could release as 0,9,27, soon"

Say next week or so, last-minute-fixes/features notwithstanding.

Thanks,

-- gr

___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel



___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Re: [Tinycc-devel] plans to 0.9.27

2017-10-11 Thread avih 
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, though I only tried them very briefly.
Thank you. 

On Wednesday, October 11, 2017 8:20 PM, Steffen Nurpmeso 
 wrote:
 

 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.c was made static to
 |  avoid some issue with inline asm that I didn't try to fix
 |* no diff -I option anymore to make tests work with busybox
 |* a patch to tccrun.c for better selinux support.
 |
 |With these changes, tcc now seems to build and pass all tests
 |cleanly on Alpine musl x86_64 standard-grsec and vanilla too,
 |configured with
 |    ./configure --config-musl --with-selinux
 |optionally also with
 |    --disable-static and/or --cc=tcc (once it was installed)

Now really: boah!  That is great!  I had it in the queue to see if
i would get my head around what Michael Matz sent, but that is
gigantic, thank you!  I will have a look and happily try that
soon.
Ciao!

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter          he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel


   ___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Re: [Tinycc-devel] plans to 0.9.27

2017-10-11 Thread Steffen Nurpmeso 
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.c was made static to
 |   avoid some issue with inline asm that I didn't try to fix
 |* no diff -I option anymore to make tests work with busybox
 |* a patch to tccrun.c for better selinux support.
 |
 |With these changes, tcc now seems to build and pass all tests
 |cleanly on Alpine musl x86_64 standard-grsec and vanilla too,
 |configured with
 |./configure --config-musl --with-selinux
 |optionally also with
 |--disable-static and/or --cc=tcc (once it was installed)

Now really: boah!  That is great!  I had it in the queue to see if
i would get my head around what Michael Matz sent, but that is
gigantic, thank you!  I will have a look and happily try that
soon.
Ciao!

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Re: [Tinycc-devel] plans to 0.9.27

2017-10-11 Thread grischka 

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 char test, plus some other
stuff.

Also, I removed the win32/Makefile (thanks to Christian's OK),
and the VIP patch (it is just not how it should work), and the
-iwithprefix option (what was the point without -iprefix).

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.c was made static to
  avoid some issue with inline asm that I didn't try to fix
* no diff -I option anymore to make tests work with busybox
* a patch to tccrun.c for better selinux support.

With these changes, tcc now seems to build and pass all tests
cleanly on Alpine musl x86_64 standard-grsec and vanilla too,
configured with
   ./configure --config-musl --with-selinux
optionally also with
   --disable-static and/or --cc=tcc (once it was installed)

Patch is here:
http://repo.or.cz/tinycc.git/commitdiff/da8c62f75d893449e232944fc62566c020b4d010

You might realize that I bumped the 'master' branch too, which
is meant to mean:
"This could be what we could release as 0,9,27, soon"

Say next week or so, last-minute-fixes/features notwithstanding.

Thanks,

-- gr

___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Re: [Tinycc-devel] plans to 0.9.27 (was 0.9.28)

2017-09-25 Thread grischka 

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 with gcc 6.3.

I found the problem is tcctest.c:test_high_clobbers()

I have no idea what is wrong with what or whether at all but we
might just #ifdef out this test for windows.

-- gr

___
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Re: [Tinycc-devel] plans to 0.9.27 (was 0.9.28)

2017-09-24 Thread Christian Jullien 
I only have a remote access on aarch64 using my gccfarm account and I
confess I don't test all commits.

Your suggestion:
-   char b;
+   signed char b;

Fixes it, you can push this change


-Original Message-
From: grischka [mailto:gris...@gmx.de] 
Sent: dimanche 24 septembre 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 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 below might fix it.  (I still wonder whether
it did work earlier (and then why) or if it just wasn't tested at all yet on
arm64).

- tests/tests2/95_bitfields.c
- index 683becf..f025c57 100644 @@ -69,9 +69,9 @@
  #elif TEST == 6
  {
  struct M P __s {
int a;
-   char b;
+   signed char b;
int x : 12, y : 4, : 0, : 4, z : 3;
char d;
  };
  TEST_STRUCT(1,2,3,4,-3);

-- gr


> jullien@gcc113:~/tinycc$ uname -a
> Linux gcc113 3.13.0-92-generic #139-Ubuntu SMP Tue Jun 28 20:45:34 UTC 
> 2016
> aarch64 aarch64 aarch64 GNU/Linux
> 
> Test: 95_bitfields...
> --- 95_bitfields.expect 2017-09-24 10:50:04.240209938 -0700
> +++ 95_bitfields.output 2017-09-24 10:50:43.236414994 -0700
> @@ -31,7 +31,7 @@
>   TEST 6 
>  bits in use : 007000FF  bits as set : 
> 0030002001FD0004
> -values  : 01 02 03 04 fffd
> +values  : 01 02 03 04 fd
>  align/size  : 4 12
> 
> 
> @@ -69,7 +69,7 @@
>   TEST 6 - PACKED 
>  bits in use : 007000FF
>  bits as set : 0030002001FD0004
> -values  : 01 02 03 04 fffd
> +values  : 01 02 03 04 fd
>  align/size  : 1 10
> 
> 
> @@ -107,7 +107,7 @@
>   TEST 6 - WITH ALIGN 
>  bits in use : 007000FF  bits as set : 
> 0030002001FD0004
> -values  : 01 02 03 04 fffd
> +values  : 01 02 03 04 fd
>  align/size  : 4 12
> 
> 
> @@ -145,5 +145,5 @@
>   TEST 6 - PACKED - WITH ALIGN   bits in use : 
> 007000FF  bits as set : 0030002001FD0004
> -values  : 01 02 03 04 fffd
> +values  : 01 02 03 04 fd
>  align/size  : 1 10
> make[2]: *** [95_bitfields.test] Error 1
> Test: 95_bitfields_ms...
> --- 95_bitfields_ms.expect  2017-09-24 10:50:04.240209938 -0700
> +++ 95_bitfields_ms.output  2017-09-24 10:50:43.246414020 -0700
> @@ -31,7 +31,7 @@
>   TEST 6 - MS-BITFIELDS 
>  bits in use : 007000FF
>  bits as set : 0030200100FD0004
> -values  : 01 02 03 04 fffd
> +values  : 01 02 03 04 fd
>  align/size  : 4 20
> 
> 
> @@ -69,7 +69,7 @@
>   TEST 6 - MS-BITFIELDS - PACKED   bits in use : 
> 70FF  bits as set : 
> 302001FD0004
> -values  : 01 02 03 04 fffd
> +values  : 01 02 03 04 fd
>  align/size  : 1 14
> 
> 
> @@ -107,7 +107,7 @@
>   TEST 6 - MS-BITFIELDS - WITH ALIGN   bits in use : 
> 007000FF
>  bits as set : 0030200100FD0004
> -values  : 01 02 03 04 fffd
> +values  : 01 02 03 04 fd
>  align/size  : 4 20
> 
> 
> @@ -145,5 +145,5 @@
>   TEST 6 - MS-BITFIELDS - PACKED - WITH ALIGN   bits in use : 
> 70FF  bits as set : 
> 302001FD0004
> -values  : 01 02 03 04 fffd
> +values  : 01 02 03 04 fd
>  align/size  : 1 14
> make[2]: *** [95_bitfields_ms.test] Error 1
> 
> -Original Message-
> From: Tinycc-devel 
> [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org]
> On Behalf Of Christian Jullien
> Sent: dimanche 24 septembre 2017 19:40
> To: 'grischka'; tinycc-devel@nongnu.org
> Subject: Re: [Tinycc-devel] plans to 0.9.28
> 
> Very nice indeed.
> 
> I offer you my time to test every attempts on:
> 
> Windows x86/x64
> Linux x86/x64
> RPi arm
> Aarch64
> 
> 
> -Original Message-
> From: grischka [mailto:gris...@gmx.de]
> Sent: dimanche 24 septembre 2017 19:10
> To: Christian JULLIEN; tinycc-devel@nongnu.org
> Subject: Re: [Tinycc-devel] plans to 0.9.28
> 
> Hi,
> 
> I just pushed a patch for more complete 'long' support (which was 
> started by Matthias Gatto for _Generic), as well as with eome 
> improvements for multicharacter constants:
> 
> http://repo.or.cz/tinycc.git/commitdiff/1443039416dd02750765

Re: [Tinycc-devel] plans to 0.9.27 (was 0.9.28)

2017-09-24 Thread grischka 

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 below might fix it.  (I still
wonder whether it did work earlier (and then why) or if it just wasn't
tested at all yet on arm64).

- tests/tests2/95_bitfields.c -
index 683becf..f025c57 100644
@@ -69,9 +69,9 @@
 #elif TEST == 6
 {
 struct M P __s {
int a;
-   char b;
+   signed char b;
int x : 12, y : 4, : 0, : 4, z : 3;
char d;
 };
 TEST_STRUCT(1,2,3,4,-3);

-- gr



jullien@gcc113:~/tinycc$ uname -a
Linux gcc113 3.13.0-92-generic #139-Ubuntu SMP Tue Jun 28 20:45:34 UTC 2016
aarch64 aarch64 aarch64 GNU/Linux

Test: 95_bitfields...
--- 95_bitfields.expect 2017-09-24 10:50:04.240209938 -0700
+++ 95_bitfields.output 2017-09-24 10:50:43.236414994 -0700
@@ -31,7 +31,7 @@
  TEST 6 
 bits in use : 007000FF
 bits as set : 0030002001FD0004
-values  : 01 02 03 04 fffd
+values  : 01 02 03 04 fd
 align/size  : 4 12


@@ -69,7 +69,7 @@
  TEST 6 - PACKED 
 bits in use : 007000FF
 bits as set : 0030002001FD0004
-values  : 01 02 03 04 fffd
+values  : 01 02 03 04 fd
 align/size  : 1 10


@@ -107,7 +107,7 @@
  TEST 6 - WITH ALIGN 
 bits in use : 007000FF
 bits as set : 0030002001FD0004
-values  : 01 02 03 04 fffd
+values  : 01 02 03 04 fd
 align/size  : 4 12


@@ -145,5 +145,5 @@
  TEST 6 - PACKED - WITH ALIGN 
 bits in use : 007000FF
 bits as set : 0030002001FD0004
-values  : 01 02 03 04 fffd
+values  : 01 02 03 04 fd
 align/size  : 1 10
make[2]: *** [95_bitfields.test] Error 1
Test: 95_bitfields_ms...
--- 95_bitfields_ms.expect  2017-09-24 10:50:04.240209938 -0700
+++ 95_bitfields_ms.output  2017-09-24 10:50:43.246414020 -0700
@@ -31,7 +31,7 @@
  TEST 6 - MS-BITFIELDS 
 bits in use : 007000FF
 bits as set : 0030200100FD0004
-values  : 01 02 03 04 fffd
+values  : 01 02 03 04 fd
 align/size  : 4 20


@@ -69,7 +69,7 @@
  TEST 6 - MS-BITFIELDS - PACKED 
 bits in use : 70FF
 bits as set : 302001FD0004
-values  : 01 02 03 04 fffd
+values  : 01 02 03 04 fd
 align/size  : 1 14


@@ -107,7 +107,7 @@
  TEST 6 - MS-BITFIELDS - WITH ALIGN 
 bits in use : 007000FF
 bits as set : 0030200100FD0004
-values  : 01 02 03 04 fffd
+values  : 01 02 03 04 fd
 align/size  : 4 20


@@ -145,5 +145,5 @@
  TEST 6 - MS-BITFIELDS - PACKED - WITH ALIGN 
 bits in use : 70FF
 bits as set : 302001FD0004
-values  : 01 02 03 04 fffd
+values  : 01 02 03 04 fd
 align/size  : 1 14
make[2]: *** [95_bitfields_ms.test] Error 1

-Original Message-
From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org]
On Behalf Of Christian Jullien
Sent: dimanche 24 septembre 2017 19:40
To: 'grischka'; tinycc-devel@nongnu.org
Subject: Re: [Tinycc-devel] plans to 0.9.28

Very nice indeed.

I offer you my time to test every attempts on:

Windows x86/x64
Linux x86/x64
RPi arm
Aarch64


-Original Message-
From: grischka [mailto:gris...@gmx.de]
Sent: dimanche 24 septembre 2017 19:10
To: Christian JULLIEN; tinycc-devel@nongnu.org
Subject: Re: [Tinycc-devel] plans to 0.9.28

Hi,

I just pushed a patch for more complete 'long' support (which was started by
Matthias Gatto for _Generic), as well as with eome improvements for
multicharacter constants:

http://repo.or.cz/tinycc.git/commitdiff/1443039416dd02750765efde1af35e31c8d4
1be3

So, now, basically, I'd agree to, including the offer to undertake the
necessary steps, to release this, say after some weeks of for finel testing,
as
 ___ 0.9.27 ___.

What do people think?

-- gr

Christian JULLIEN wrote:

Hi all,


Last December, we where close to release 0.9.28 but more than 6 months 
later, I see no plans for an imminent 0.9.28 release.


I'm fortunate to know how to build tcc on the many machines I use but 
also see many users trying to use a very old 0.9.27 version.


I think it's time to release 0.9.28 and start new dev. on 0.9.29 IMHO,

- we should decide what we really want to implement before we release
0.9.28 and propose an ETA for implementation

- enter a bug fix, validation cycle (no new feature or gratuitous
changes)

- check all ports (Windows 32/64, Linux x86, x64, arm, Aarch64, 
more?), I will test all of them


- Make 0.9.28


Sounds reasonable to you?


--
--

__