[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Tinycc-devel] Fixed an issue with switch/case statements on unsigne
|
From: |
Christian Jullien |
|
Subject: |
Re: [Tinycc-devel] Fixed an issue with switch/case statements on unsigned 64 bits |
|
Date: |
Wed, 19 Aug 2020 21:52:36 +0200 |
It has been fixed.
You can see if something is broken with "make test".
Sometimes it fails on another platform. i.e. if you fix something on Linux x64
it may fail on Windows or macOS.
Ideally, every commit should be tested on : Linux x86/x64/arm/aarch64/riscv64,
Windows x86/x64, macOS x64.
I personally test nearly every commits on : Linux arm/aarch64, Windows x86/x64,
macOS x64.
And less often on Linux x86/x64.
-----Original Message-----
From: Tinycc-devel [mailto:tinycc-devel-bounces+eligis=orange.fr@nongnu.org] On
Behalf Of Willy Tarreau
Sent: Wednesday, August 19, 2020 21:13
To: Alexander Strasser
Cc: tinycc-devel@nongnu.org
Subject: Re: [Tinycc-devel] Fixed an issue with switch/case statements on
unsigned 64 bits
Hi Alexander, hi Christian,
On Wed, Aug 19, 2020 at 08:42:00PM +0200, Alexander Strasser wrote:
> Hi Christian,
>
> did you put Willy in Cc?
>
> If yes, sorry for the noise.
Ah indeed, no I wasn't apparently, thanks!
> On 2020-08-18 18:45 +0200, Christian JULLIEN wrote:
> > Recent change has an issue with some tests
> >
> > macOS x64 and Linux ARM------------ test3 ------------tcctest.c:1939:
> > error: duplicate case valuemake[2]: *** [test3] Error 1------------ memtest
> > ------------../tests/tcctest.c:1939: error: duplicate case valuemake[2]:
> > *** [memtest] Error 1
> > Linux Aarch64:../arm64-gen.c:1382: error: duplicate case valuemake[2]: ***
> > [Makefile:107: libtest_mt] Error 1------------ test3 ------------In file
> > included from ../tcc.c:23:In file included from
> > ../libtcc.c:35:../arm64-gen.c:1382: error: duplicate case valuemake[2]: ***
> > [Makefile:139: test3] Error 1------------ memtest ------------
Ah bad, sorry about that! How can I run these tests ? I didn't notice
them while trying to proceed correctly. I'd like to fix these if at
all possible!
Thank you!
Willy
(please keep me in CC :-))
_______________________________________________
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel