Re: [Tinycc-devel] test failures on win32 x86-64

[Domingo Alvarez Duarte]

Thank you !

I just accepted it and I'm waiting for an answer here 
https://github.com/repo-sync/github-sync/issues/104 to add something 
like I did here 
https://github.com/mingodad/tinycc/actions/runs/1638429826/workflow .

On 14/10/22 11:12, Vlad Vissoultchev wrote:
> Just sent you an invitation from  https://github.com/orgs/TinyCC org.
>
> In mob development fashion every member of the org has owner rights and can 
> invite other people to configure CI for instance or anything needed.
>
> cheers,
> </wqw>
>
> -----Original Message-----
> From: Tinycc-devel [mailto:tinycc-devel-bounces+wqweto=gmail.com@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 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 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 tcc compiling itself, or the compiled tcc compiling
> > tcctest, or is it tcctest running, or even is it maybe gcc that
> > crashes?
> >
> > You can see the command when you call the test directly:
> >
> >     make -C tests clean
> >     make -C tests test1
> >
> > > from tests/tests2/:
> > > - 104_inline.test
> > This might be fixed on mob.
> >
> > --- grischka
> >
> > > I sampled several revisions since release_0_9_27, and all of them
> > > fail somehow, mostly in tests (one revision also failed to build).
> > >
> > > This could be related to the mingw gcc I'm testing with - gcc 11.3.0
> > > using mingw64 in MSYS2. I _think_ the x86-64 win32 tests did pass in
> > > thepast, so if someone could confirm the failures it may help.
> > >
> > > I tested as follows on Windows 10:
> > > - launch the mingw64 MSYS2 desktop shortcut
> > > - cd path/to/tinycc
> > > - git clean -xfd
> > > - ./configure --cpu=x86_64 --config-mingw32 && make && make test
> > >
> > >
> > > regards,
> > > avih
> > >
> > > _______________________________________________
> > > 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
>
>
> _______________________________________________
> Tinycc-devel mailing list
> Tinycc-devel@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/tinycc-devel