From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>,
Jesper Dangaard Brouer <hawk@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
netdev@vger.kernel.org, bpf@vger.kernel.org,
oss-drivers@netronome.com, linux-kernel@vger.kernel.org,
xdp-newbies@vger.kernel.org, valdis@vt.edu
Subject: Re: netronome/nfp/bpf/jit.c cannot be build with -O3
Date: Mon, 06 May 2019 23:24:39 +0200 [thread overview]
Message-ID: <2a3761669e4ec13847205d30384c0a17@natalenko.name> (raw)
In-Reply-To: <20190506140022.188d2b84@cakuba.hsd1.ca.comcast.net>
Hi.
On 06.05.2019 23:00, Jakub Kicinski wrote:
> Any chance you could try different compiler versions? The code in
> question does not look too unusual. Could you try if removing
> FIELD_FIT() on line 326 makes a difference?
If building with gcc from CentOS 7:
gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-36)
the issue is not reproducible.
Also, commenting out the whole "if" block with FIELD_FIT() prevents the
issue from occurring too.
--
Oleksandr Natalenko (post-factum)
next prev parent reply other threads:[~2019-05-06 21:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 19:40 netronome/nfp/bpf/jit.c cannot be build with -O3 Oleksandr Natalenko
2019-05-06 21:00 ` Jakub Kicinski
2019-05-06 21:24 ` Oleksandr Natalenko [this message]
2019-05-06 21:35 ` Jakub Kicinski
2019-05-07 5:01 ` Oleksandr Natalenko
2019-05-06 22:01 ` [oss-drivers] " Jiong Wang
2019-05-07 5:05 ` Oleksandr Natalenko
2019-05-07 11:31 ` Jiong Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2a3761669e4ec13847205d30384c0a17@natalenko.name \
--to=oleksandr@natalenko.name \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=jakub.kicinski@netronome.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--cc=songliubraving@fb.com \
--cc=valdis@vt.edu \
--cc=xdp-newbies@vger.kernel.org \
--cc=yhs@fb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).