On Fri, Jan 24, 2020 at 10:31:14AM +0100, Willy Tarreau wrote:
> This is really annoying, so much time spent dealing with bogus warnings
> is really irritating. I'm going to work around it with a cast to unsigned
> short.
>
> The worst part of it is that if it emits such a warning, who knows how
On Fri, Jan 24, 2020 at 07:12:49AM +0500, ??? wrote:
> > it was ubuntu 18.04 + gcc8, I'll try 19.10 + gcc9
> >
>
> gcc9 produces the same warning
OK, I've put my hands on an ubuntu-18.04 + gcc8 32 bits. And now I can
confirm it definitely is a gcc bug. The code is the same as a few
On Fri, Jan 24, 2020 at 07:12:49AM +0500, ??? wrote:
> ??, 24 ???. 2020 ?. ? 01:04, ??? :
>
> >
> >
> > ??, 24 ???. 2020 ?. ? 00:54, Willy Tarreau :
> >
> >> On Fri, Jan 24, 2020 at 12:46:12AM +0500, ??? wrote:
> >> > > diff --git a/Makefile b/Makefile
> >> > > index
пт, 24 янв. 2020 г. в 01:04, Илья Шипицин :
>
>
> пт, 24 янв. 2020 г. в 00:54, Willy Tarreau :
>
>> On Fri, Jan 24, 2020 at 12:46:12AM +0500, ??? wrote:
>> > > diff --git a/Makefile b/Makefile
>> > > index 8399f6ca35..4757bc77e6 100644
>> > > --- a/Makefile
>> > > +++ b/Makefile
>> > >
пт, 24 янв. 2020 г. в 00:54, Willy Tarreau :
> On Fri, Jan 24, 2020 at 12:46:12AM +0500, ??? wrote:
> > > diff --git a/Makefile b/Makefile
> > > index 8399f6ca35..4757bc77e6 100644
> > > --- a/Makefile
> > > +++ b/Makefile
> > > @@ -199,6 +199,7 @@ SPEC_CFLAGS += $(call
>
On Fri, Jan 24, 2020 at 12:46:12AM +0500, ??? wrote:
> > diff --git a/Makefile b/Makefile
> > index 8399f6ca35..4757bc77e6 100644
> > --- a/Makefile
> > +++ b/Makefile
> > @@ -199,6 +199,7 @@ SPEC_CFLAGS += $(call cc-opt,-Wshift-negative-value)
> > SPEC_CFLAGS += $(call
чт, 23 янв. 2020 г. в 23:17, Willy Tarreau :
> On Thu, Jan 23, 2020 at 10:59:00PM +0500, ??? wrote:
> > > Could you please try to use (size_t) instead of (unsigned int) ? If
> it's
> > > enough to shut it up, I'm fine with doing that change. Otherwise we'll
> > > probably get rid of that
On Thu, Jan 23, 2020 at 07:41:11PM +0100, Tim Düsterhus wrote:
> Willy,
>
> Am 23.01.20 um 19:17 schrieb Willy Tarreau:
> > Thanks for the test! So basically this clearly proves we respect the
> > calling convention but the compiler still complains. OK I'm seeing in
> > the mad that it's for
Willy,
Am 23.01.20 um 19:17 schrieb Willy Tarreau:
> Thanks for the test! So basically this clearly proves we respect the
> calling convention but the compiler still complains. OK I'm seeing in
> the mad that it's for functions "decorated" with the "alloc_size"
> attribute. Thus in short they
On Thu, Jan 23, 2020 at 10:59:00PM +0500, ??? wrote:
> > Could you please try to use (size_t) instead of (unsigned int) ? If it's
> > enough to shut it up, I'm fine with doing that change. Otherwise we'll
> > probably get rid of that stupid warning.
> >
>
> CC src/server.o
> CC
чт, 23 янв. 2020 г. в 15:14, Willy Tarreau :
> On Thu, Jan 23, 2020 at 01:09:22PM +0500, ??? wrote:
> > hello,
> >
> > I tried to build using cross compiler (arm32 on amd64). sorry for
> > screenshot.
> > Willy, do you mean errors like that ?
>
> So for those not seeing the screenshot,
On Thu, Jan 23, 2020 at 03:21:40PM +0500, ??? wrote:
> also, can we treat warnings as errors for CI builds ? it would save a bunch
> of time, instead of
> looking at build log, we can watch for build status.
Yes definitely. You just have to add "ERR=1" to your "make" command line
and it
чт, 23 янв. 2020 г. в 15:14, Willy Tarreau :
> On Thu, Jan 23, 2020 at 01:09:22PM +0500, ??? wrote:
> > hello,
> >
> > I tried to build using cross compiler (arm32 on amd64). sorry for
> > screenshot.
> > Willy, do you mean errors like that ?
>
> So for those not seeing the screenshot,
On Thu, Jan 23, 2020 at 01:09:22PM +0500, ??? wrote:
> hello,
>
> I tried to build using cross compiler (arm32 on amd64). sorry for
> screenshot.
> Willy, do you mean errors like that ?
So for those not seeing the screenshot, it says:
warning: argument 1 range [2147483648, 4294967295]
hello,
I tried to build using cross compiler (arm32 on amd64). sorry for
screenshot.
Willy, do you mean errors like that ?
[image: Screenshot from 2020-01-23 13-03-49.png]
ср, 6 нояб. 2019 г. в 12:26, Willy Tarreau :
> Hi Ilya,
>
> On Tue, Nov 05, 2019 at 07:20:43PM +0500, ???
Hi Ionel,
On Mon, Nov 04, 2019 at 02:10:56PM +0100, GARDAIS Ionel wrote:
> FWIW, when I build for armhf (RaspberryPi 3b with Raspbian buster), I have to
> add -latomic to the LD_FLAGS.
It's not the case for me but I had to add it for another one, I think
it was for the mips running in my build
Hi Ilya,
On Tue, Nov 05, 2019 at 07:20:43PM +0500, ??? wrote:
> only arm64 are available.
> we can try arm using cross build, for example.
Then don't bother with this, it's likely then that they will not
have all the environment available. Maybe even their hardware does
not support
пн, 4 нояб. 2019 г. в 17:49, Willy Tarreau :
> Hi Ilya,
>
> On Mon, Nov 04, 2019 at 12:18:49AM +0500, ??? wrote:
> > hello,
> >
> > should we switch some builds to arm64?
> >
> > https://blog.travis-ci.com/2019-10-07-multi-cpu-architecture-support
>
> Ah that's interesting! I frequently
Hi,
FWIW, when I build for armhf (RaspberryPi 3b with Raspbian buster), I have to
add -latomic to the LD_FLAGS.
Ionel
- Mail original -
De: "Willy Tarreau"
À: " ???"
Cc: "haproxy"
Envoyé: Lundi 4 Novembre 2019 13:48:57
Objet: Re: arm64 bui
Hi Ilya,
On Mon, Nov 04, 2019 at 12:18:49AM +0500, ??? wrote:
> hello,
>
> should we switch some builds to arm64?
>
> https://blog.travis-ci.com/2019-10-07-multi-cpu-architecture-support
Ah that's interesting! I frequently build for arm/arm64 but I agree
it would be nice to have this
20 matches
Mail list logo
