[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <03db016e-5337-0207-3d17-0b3bbe79fa5c@cogentembedded.com>
Date: Sun, 13 Oct 2019 20:06:24 +0300
From: Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
To: ast@...nel.org, daniel@...earbox.net, yhs@...com,
davem@...emloft.net, jakub.kicinski@...ronome.com, hawk@...nel.org,
john.fastabend@...il.com, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, bpf@...r.kernel.org,
clang-built-linux@...glegroups.com, ilias.apalodimas@...aro.org
Subject: Re: [PATCH v5 bpf-next 09/15] samples/bpf: use own flags but not
HOSTCFLAGS
On 13.10.2019 0:26, Ivan Khoronzhuk wrote:
>>>>> While compiling natively, the host's cflags and ldflags are equal to
>>>>> ones used from HOSTCFLAGS and HOSTLDFLAGS. When cross compiling it
>>>>> should have own, used for target arch. While verification, for arm,
>>>>
>>>> While verifying.
>>> While verification stage.
>>
>> While *in* verification stage, "while" doesn't combine with nouns w/o
>> a preposition.
>
>
> Sergei, better add me in cc list when msg is to me I can miss it.
Hm, the earlier mails were addressed to you but no the last one --
not sure what happened there, sorry.
> Regarding the language lesson, thanks, I will keep it in mind next
> time, but the issue is not rude, if it's an issue at all, so I better
> leave it as is, as not reasons to correct it w/o code changes and
> everyone is able to understand it.
Up to you. and the maintainer(s)...
>>>>> arm64 and x86_64 the following flags were used always:
>>>>>
>>>>> -Wall -O2
>>>>> -fomit-frame-pointer
>>>>> -Wmissing-prototypes
>>>>> -Wstrict-prototypes
>>>>>
>>>>> So, add them as they were verified and used before adding
>>>>> Makefile.target and lets omit "-fomit-frame-pointer" as were proposed
>>>>> while review, as no sense in such optimization for samples.
>>>>>
>>>>> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@...aro.org>
>>>> [...]
MBR, Sergei
Powered by blists - more mailing lists