Bug#873508: sparse test failures on ppc32le (and other not so common archs)

On Wed, Jan 09, 2019 at 09:28:54PM -0500, Antoine Beaupré wrote: > Control: forwarded -1 https://github.com/br101/horst/issues/93 Hi, The issue showed there, more precisely the one: /usr/include/x86_64-linux-gnu/bits/mathcalls-helper-functions.h:21:1: error: Expected ) in function declarator

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

Control: forwarded -1 https://github.com/br101/horst/issues/93 On 2017-09-01 10:46:44, Uwe Kleine-König wrote: > Hello, > > On Thu, Aug 31, 2017 at 11:43:53PM +0100, Ramsay Jones wrote: >> On 31/08/17 21:55, Uwe Kleine-König wrote: >> > On Wed, Aug 30, 2017 at 08:11:49PM -0400, Christopher Li

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

Hello, On 08/30/2017 06:14 PM, Uwe Kleine-König wrote: > Antoine Beaupre (on Cc:) noticed that sparse doesn't work on some not so > common architectures like ppc32le, s390x, ppc64 and sparc64[1]. This is > nicely catched by the testsuite, e.g.: > > [..] Just a heads up: I uploaded 0.5.2 to

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

On Wed, Sep 27, 2017 at 10:00 AM, Uwe Kleine-König wrote: > Hello, > > On Tue, Sep 26, 2017 at 08:11:01PM +0200, Uwe Kleine-König wrote: >> And ppc64 and x32 need the respective cpp defines added I think. If >> noone beats me to it, I will look into the latter at least

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

Hello, On Tue, Sep 26, 2017 at 08:11:01PM +0200, Uwe Kleine-König wrote: > And ppc64 and x32 need the respective cpp defines added I think. If > noone beats me to it, I will look into the latter at least during the > next few days. Looking at ppc64, the following fixes the build: diff --git

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

Control: severity 873508 normal Control: retitle 873508 Fix FTBFS for m68k, hurd, x32 and ppc64 On Thu, Sep 21, 2017 at 08:58:23PM +0200, Uwe Kleine-König wrote: > I still expect some platforms to fail with the wrapper, too, because > cgcc doesn't know about all platforms yet. But I intend to

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

Control: clone 873508 -1 Control: retitle -1 Please use cgcc to check hosted C code instead of sparse Control: severity -1 normal Control: reassign -1 horst On Fri, Sep 01, 2017 at 09:46:44AM +0200, Uwe Kleine-König wrote: > @anarcat: Given that cgcc seems to work, would you agree to apply the >

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

On Tue, Sep 12, 2017 at 2:27 AM, Uwe Kleine-König wrote: >> BTW, if I want to get a PPC64 machine for Linux testing purpose, is the >> used apple G5 a good place to start? > > Honestly I don't know. https://wiki.debian.org/ppc64el tells > > Debian/ppc64el

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

On Tue, Sep 12, 2017 at 01:59:47AM -0400, Christopher Li wrote: > On Wed, Sep 6, 2017 at 11:36 AM, Uwe Kleine-König > wrote: > > There is https://dsa.debian.org/doc/guest-account/ which would give you > > the possibility to access some Debian machines. Other than that I

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

On Wed, Sep 6, 2017 at 11:36 AM, Uwe Kleine-König wrote: > There is https://dsa.debian.org/doc/guest-account/ which would give you > the possibility to access some Debian machines. Other than that I intend Sorry for the delay. Thanks for the pointer of the guest account.

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

On Sun, Sep 10, 2017 at 10:43 AM, Uwe Kleine-König wrote: > >> Meanwhile, is it possible to have the build logs but with 'make V=1 ...' ? >> It would also be useful to have: >> - the output of 'uname -a' >> - the details about the version of LLVM you're using > > Sure, can

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

On Sun, Sep 10, 2017 at 10:43 AM, Uwe Kleine-König wrote: > On 09/10/2017 03:22 AM, Luc Van Oostenryck wrote: >> >> I fully test on x86, x86-64, arm & ARM64 (with LLVM 3.9 or 4.0). >> I also test on ppc64 but not the LLVM part because the machines I have >> access to have

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

On 09/10/2017 03:22 AM, Luc Van Oostenryck wrote: > On Sat, Sep 9, 2017 at 11:02 PM, Uwe Kleine-König > wrote: >> >> I tried this on ppc64le and it fixes 2 tests, so were at >> >> Out of 287 tests, 273 passed, 14 failed (10 of them are known to >> fail) >> >> The

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

On Sat, Sep 9, 2017 at 11:02 PM, Uwe Kleine-König wrote: > > I tried this on ppc64le and it fixes 2 tests, so were at > > Out of 287 tests, 273 passed, 14 failed (10 of them are known to fail) > > The repaired tests are: > > backend/hello.c >

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

On Thu, Aug 31, 2017 at 08:47:55PM -0400, Christopher Li wrote: > On Thu, Aug 31, 2017 at 4:55 PM, Uwe Kleine-König Yes > that works. So to address the Debian bug I can do: > > > > - move sparse to /usr/lib > > - teach cgcc about the move of sparse > > - make /usr/bin/sparse call

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

Hello Christopher, On Wed, Sep 06, 2017 at 11:18:04AM -0400, Christopher Li wrote: > On Wed, Sep 6, 2017 at 10:44 AM, Uwe Kleine-König > wrote: > > and while it's ok to test the core stuff and not wanting the system > > includes to interfere, there should also be tests

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

On Wed, Sep 6, 2017 at 10:44 AM, Uwe Kleine-König wrote: > > and while it's ok to test the core stuff and not wanting the system > includes to interfere, there should also be tests that check "ordinary" > userspace programs which naturally depend on the system headers. >

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

[readding people to Cc assuming that's ok] Hello Luc, On Mon, Sep 04, 2017 at 10:36:47PM +0200, Luc Van Oostenryck wrote: > On Mon, Sep 4, 2017 at 10:57 AM, Uwe Kleine-König > wrote: > > On 09/03/2017 11:14 PM, Luc Van Oostenryck wrote: > >> On Fri, Sep 1, 2017 at 9:02

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

On Sun, Sep 3, 2017 at 5:14 PM, Luc Van Oostenryck wrote: > > I really think that the testsuite should not depend on system or library > header. I think that is a good point. We can start cleaning up the system header file dependency in the existing test suite. See

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

On Fri, Sep 1, 2017 at 9:02 AM, Josh Triplett wrote: > On Thu, Aug 31, 2017 at 08:47:55PM -0400, Christopher Li wrote: >> On Thu, Aug 31, 2017 at 4:55 PM, Uwe Kleine-König Yes >> that works. So to address the Debian bug I can do: >> > >> > - move sparse to

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

On Fri, Sep 01, 2017 at 09:57:09AM +0200, Uwe Kleine-König wrote: > On Fri, Sep 01, 2017 at 12:02:12AM -0700, Josh Triplett wrote: > > On Thu, Aug 31, 2017 at 08:47:55PM -0400, Christopher Li wrote: > > > On Thu, Aug 31, 2017 at 4:55 PM, Uwe Kleine-König Yes > > > that works. So to

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

On Fri, Sep 1, 2017 at 3:02 AM, Josh Triplett wrote: >> First of all. It is not very trivial to teach sparse about the architecture >> stuff. To my mind, we need to move all the cgcc logic into sparse. > > Related to that: while it would mean we couldn't necessarily just

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

On Fri, Sep 1, 2017 at 3:46 AM, Uwe Kleine-König wrote: \> > Nearly right. I'm responsible for the sparse Debian package and the > problem at hand is https://bugs.debian.org/873508. This bug report has > "Severity: serious" wihch might eventually result in the removal of >

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

On 2017-09-01 09:46:44, Uwe Kleine-König wrote: > Hello, > > On Thu, Aug 31, 2017 at 11:43:53PM +0100, Ramsay Jones wrote: >> On 31/08/17 21:55, Uwe Kleine-König wrote: >> > On Wed, Aug 30, 2017 at 08:11:49PM -0400, Christopher Li wrote: >> >> That is very much like on x86_64 missing define

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

On Fri, Sep 01, 2017 at 12:02:12AM -0700, Josh Triplett wrote: > On Thu, Aug 31, 2017 at 08:47:55PM -0400, Christopher Li wrote: > > On Thu, Aug 31, 2017 at 4:55 PM, Uwe Kleine-König Yes > > that works. So to address the Debian bug I can do: > > > > > > - move sparse to /usr/lib > >

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

Hello, On Thu, Aug 31, 2017 at 11:43:53PM +0100, Ramsay Jones wrote: > On 31/08/17 21:55, Uwe Kleine-König wrote: > > On Wed, Aug 30, 2017 at 08:11:49PM -0400, Christopher Li wrote: > >> That is very much like on x86_64 missing define "#weak_define __x86_64__ 1" > >> > >> Does cgcc work for you?

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

On Thu, Aug 31, 2017 at 08:47:55PM -0400, Christopher Li wrote: > On Thu, Aug 31, 2017 at 4:55 PM, Uwe Kleine-König Yes > that works. So to address the Debian bug I can do: > > > > - move sparse to /usr/lib > > - teach cgcc about the move of sparse > > - make /usr/bin/sparse call

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

On Thu, Aug 31, 2017 at 6:43 PM, Ramsay Jones >> - move sparse to /usr/lib >> - teach cgcc about the move of sparse >> - make /usr/bin/sparse call cgcc -no-compile "$@" > > Hmm, I don't think that would be a good idea ... > Agree. > > Anyway, if you were to un-install llvm, sparse-llvm etc.,

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

On Thu, Aug 31, 2017 at 4:55 PM, Uwe Kleine-König Yes that works. So to address the Debian bug I can do: > > - move sparse to /usr/lib > - teach cgcc about the move of sparse > - make /usr/bin/sparse call cgcc -no-compile "$@" I don't like that. It means the user can't invoke

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

On 31/08/17 21:55, Uwe Kleine-König wrote: > On Wed, Aug 30, 2017 at 08:11:49PM -0400, Christopher Li wrote: >> That is very much like on x86_64 missing define "#weak_define __x86_64__ 1" >> >> Does cgcc work for you? In the future we do want to move the archetecture >> related define from cgcc

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

Hello Christopher, On Wed, Aug 30, 2017 at 08:11:49PM -0400, Christopher Li wrote: > On Wed, Aug 30, 2017 at 1:36 PM, Uwe Kleine-König > wrote: > >> > > >> > diff --git a/validation/backend/sum.c b/validation/backend/sum.c > >> > index 0604299..d0be8dd 100644 > >> > ---

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

On Wed, Aug 30, 2017 at 1:36 PM, Uwe Kleine-König wrote: >> > >> > diff --git a/validation/backend/sum.c b/validation/backend/sum.c >> > index 0604299..d0be8dd 100644 >> > --- a/validation/backend/sum.c >> > +++ b/validation/backend/sum.c >> > @@ -1,3 +1,5 @@ >> >

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

Hello, On Wed, Aug 30, 2017 at 05:55:00PM +0100, Ramsay Jones wrote: > On 30/08/17 17:14, Uwe Kleine-König wrote: > > ukleinek@plummer:~/sparse$ make check V=1 > > It would be easier to see the results if you _didn't_ add V=1. ;-) noted for the next time. > [snip] > > Out of 287 tests,

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

On 30/08/17 17:14, Uwe Kleine-König wrote: > Hello, > > Antoine Beaupre (on Cc:) noticed that sparse doesn't work on some not so > common architectures like ppc32le, s390x, ppc64 and sparc64[1]. This is > nicely catched by the testsuite, e.g.: The only architecture, from the above list, that

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

Hello, Antoine Beaupre (on Cc:) noticed that sparse doesn't work on some not so common architectures like ppc32le, s390x, ppc64 and sparc64[1]. This is nicely catched by the testsuite, e.g.: ukleinek@plummer:~/sparse$ git rev-parse HEAD 958c11c35d98417eb6b948bffe2dffed14eb3320