Hi,
Improvements are possible in this area but
cgcc -E test.c -o test.C -MF test.d
is not supposed to work as expected by OP since
gcc -E test.c -o test.C -MF test.d
is not working.
So, it's not a bug and this PR should be closed.
Best regards,
-- Luc Van Oostenryck
On Tue, Jan 29, 2019 at 12:57:09PM -0800, Jonathan Nieder wrote:
> Hi Uwe,
>
> Uwe Kleine-König wrote:
> > On 1/29/19 2:38 AM, Jonathan Nieder wrote:
>
> >> Thoughts of all kinds welcome, as always. If you'd prefer this in the
> >> form of a "git pull"-able repository, a push to salsa, or an NMU
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
i
On Tue, Sep 25, 2018 at 04:38:01PM +0200, Uwe Kleine-König wrote:
> > By *default*, if no -gcc-base-dir is used, sparse use the same dir
> > as the one used by the GCC used to compile sparse itself. It's only
> > this default that is hardcoded.
>
> I wasn't sure if this is expected to work. I had
On Fri, Sep 14, 2018 at 09:45:44PM +0200, Uwe Kleine-König wrote:
> Hello,
>
> [Cc += sparse mailing list]
Sorry for the late answer.
> > > Santiago Vila wrote...
> > >
> > > > make -j1 check
> > > > make[1]: Entering directory '/<>'
> > > > sparse -g -O2 -fdebug-prefix-map=/<>=.
> >
On Fri, Apr 27, 2018 at 09:33:55AM +0200, Uwe Kleine-König wrote:
> On 04/27/2018 09:33 AM, Luc Van Oostenryck wrote:
> > On Fri, Apr 27, 2018 at 07:56:38AM +0200, Uwe Kleine-König wrote:
> >> Hello,
> >>
> >>> [..]
> >>
> >> Just a heads u
On Fri, Apr 27, 2018 at 07:56:38AM +0200, Uwe Kleine-König wrote:
> 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
On Fri, Apr 27, 2018 at 07:56:38AM +0200, Uwe Kleine-König wrote:
> 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
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 during the
>> next few days.
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 do. Attached is a build
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 t
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
> backend/sum.c
>
> unexpected f
hen doing a native build. Using some sort of spec file or a .sparserc
can help too.
I also note that currently, sparse is already largely universal *because*
it *doesn't* need those platform details (or only the very minimal: word size).
-- Luc Van Oostenryck
13 matches
Mail list logo
