Hello,
On Thu, 20 Oct 2022, avih wrote:
> "dec %edi" truncates the %rdi register to 32bit by zero-extension,
> so that ... this is now segfault. That only matters if the stack
> (which %rdi points into) is setup such that it's beyond 32bit,
> which ... is indeed the case on win10 for you. So,
On Wednesday, October 19, 2022, 03:36:59 PM GMT+3, Michael Matz
wrote:
> ...
> "dec %edi" truncates the %rdi register to 32bit by zero-extension,
> so that ... this is now segfault. That only matters if the stack
> (which %rdi points into) is setup such that it's beyond 32bit,
> which ... is
Hi,
On Wed, 19 Oct 2022, Domingo Alvarez Duarte wrote:
Looking through the code on "tests/tcctest.c" there is more places using
"[unsigned] long" that probably will need to be revised to use "[unsigned]
long long" or "size_t".
Nah, you can't just blindly grep for "long" and randomly replace
Looking through the code on "tests/tcctest.c" there is more places using
"[unsigned] long" that probably will need to be revised to use
"[unsigned] long long" or "size_t".
Probably in several other places see bellow for a search on my fork:
=
va_list.c
extern void *memcpy(void *dest,
Hello Michael !
Thank you for your great work !
I applied your changes to my fork but the tests continue to fail on
window see the result here
https://github.com/mingodad/tinycc/actions/runs/3282234645/jobs/5405354710 .
Cheers !
On 19/10/22 14:36, Michael Matz wrote:
Hello,
On Fri, 14
Hello,
On Fri, 14 Oct 2022, avih via Tinycc-devel wrote:
0x7ff72b42b266 <+50>: repnz scas %es:(%rdi),%al
0x7ff72b42b268 <+52>: dec %edi
This is the problem. "dec %edi" truncates the %rdi register to 32bit by
zero-extension, so that ...
0x7ff72b42b26a <+54>: mov
On Friday, October 14, 2022, 05:27:47 PM GMT+3, grischka
wrote:
>> and indeed, when tcc64 is compiled using tcc64 then on win10
>> s->sh_addr is ~22 bits, and all tests do pass _before_ d76e0323.
>
> Well, maybe behavior of malloc on Win10 has to do with the image-base
> of the process. (see
On 14.10.2022 11:24, avih via Tinycc-devel wrote:
So somehow, on win7 the address from malloc is always ~22 bits,
while on win10 msvc and new mingw gcc procude ~43 bits address,
while with tcc and old gcc malloc returns ~22 bits addresses.
and indeed, when tcc64 is compiled using tcc64 then on
It seems that something changed on windows itself because my fork was
passing the tests before and now without any substantial change is
failing see here https://github.com/mingodad/tinycc/actions , and I also
tested on Windows7 32 bits and all tests pass.
On 14/10/22 11:24, avih via
The github action is already working and the windows tests failed see
then here https://github.com/TinyCC/tinycc/actions/runs/3249532722 .
On 14/10/22 11:24, avih via Tinycc-devel wrote:
In reply to the second half of:
https://lists.nongnu.org/archive/html/tinycc-devel/2022-10/msg00021.html
>
@nongnu.org] On
Behalf Of Domingo Alvarez Duarte
Sent: Friday, October 14, 2022 10:54 AM
To: tinycc-devel@nongnu.org
Subject: Re: [Tinycc-devel] test failures on win32 x86-64
I noticed that there is a github mirror of tinycc repository, maybe it's a good
idea to set a github action there that builds
In reply to the second half of:
https://lists.nongnu.org/archive/html/tinycc-devel/2022-10/msg00021.html
> As to spurious problems with MSYS2 I can only say that in my experience
> it is not a completely reliable build system.
>
> As a derivative from cygwin it shares the same fork() emulation
-bounces+wqweto=gmail@nongnu.org] On
Behalf Of Domingo Alvarez Duarte
Sent: Friday, October 14, 2022 10:54 AM
To: tinycc-devel@nongnu.org
Subject: Re: [Tinycc-devel] test failures on win32 x86-64
I noticed that there is a github mirror of tinycc repository, maybe it's a good
idea to set a github
At 2022-10-14 15:53:56, "Domingo Alvarez Duarte" wrote:
>I noticed that there is a github mirror of tinycc repository, maybe it's
>a good idea to set a github action there that builds and test it on
>windows, mac and linux on every commit.
Maybe it is not a good idea. It seems to be synced
I noticed that there is a github mirror of tinycc repository, maybe it's
a good idea to set a github action there that builds and test it on
windows, mac and linux on every commit.
On 13/10/22 20:59, grischka wrote:
On 08.10.2022 22:39, avih via Tinycc-devel wrote:
Hi,
The following tests
On 08.10.2022 22:39, avih via Tinycc-devel wrote:
Hi,
The following tests fail for me currently (0fd7376 gnu hash) when
building tcc for win32 x86-64 (but pass when building i386)
from tests/:
- test3
- test1b
Basically we would need to know first what part of the test fails
at all. Is it
Hi,
The following tests fail for me currently (0fd7376 gnu hash) when
building tcc for win32 x86-64 (but pass when building i386)
from tests/:
- test3
- test1b
from tests/tests2/:
- 104_inline.test
I sampled several revisions since release_0_9_27, and all of them
fail somehow, mostly in tests
17 matches
Mail list logo
