> | -fno-strict-aliasing in MD is acceptable compromise for me.
>
> Until that stops working, or being available. I think we should
> let the majority decide what's appropriate.
if -fstrict-aliasing becomes the only option than we'll need a
few years to clean up the kernel.
ie, i don't think th
In article <20141119210214.GA8310@neva>,
Alexander Nasonov wrote:
>Christos Zoulas wrote:
>> Module Name: src
>> Committed By:christos
>> Date:Wed Nov 19 19:34:43 UTC 2014
>>
>> Modified Files:
>> src/sys/net: bpfjit.c
>>
>> Log Message:
>> Add BPF_MOD/BPF_XOR (unte
Christos Zoulas wrote:
> Module Name: src
> Committed By: christos
> Date: Wed Nov 19 19:34:43 UTC 2014
>
> Modified Files:
> src/sys/net: bpfjit.c
>
> Log Message:
> Add BPF_MOD/BPF_XOR (untested, needs work)
Changes look good.
> /*
> + * XXX: Until we support SLJIT_UMOD proper
On Mon, 17 Nov 2014, Masao Uebayashi wrote:
How about adding a new make variable CONFIGOPTS, which is passed to config(1)?
This name is similar to COPTS and works similarly too.
Yes, that could work.
--apb (Alan Barrett)
