All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Jiong Wang <jiong.wang@netronome.com>
Cc: xdp-newbies@vger.kernel.org, yhs@fb.com,
	iovisor-dev@lists.iovisor.org, oss-drivers@netronome.com,
	brouer@redhat.com, hans@hanshq.net
Subject: Re: [PATCH, bpf-llvm] Fix bug on silently truncating 64-bit immediate
Date: Thu, 12 Oct 2017 13:04:12 +0200	[thread overview]
Message-ID: <20171012130412.72432f87@redhat.com> (raw)
In-Reply-To: <1507803690-17709-1-git-send-email-jiong.wang@netronome.com>

On Thu, 12 Oct 2017 06:21:30 -0400
Jiong Wang <jiong.wang@netronome.com> wrote:

> We came across an llvm bug when compiling some testcases that 64-bit
> immediates are silently truncated into 32-bit and then packed into
> BPF_JMP | BPF_K encoding.  This caused comparison with wrong value.

I think you send this to the wrong mailing list... this looks like a
patch against the LLVM source code.

Shouldn't you send to: llvm-dev@lists.llvm.org ?
 
> This bug looks to be introduced by r308080.  

This looks like a very recent change:
  https://llvm.org/viewvc/llvm-project?view=revision&revision=308080
  Sat Jul 15 05:41:42 2017 UTC (2 months, 4 weeks ago)

(As you are sending this to a user mailing list: xdp-newbies@vger.kernel.org)

I want to know if this have made it into a LLVM release? and which release?

As the git-repo[1] replica of LLVM SVN-repo does not git-tag the
releases, I could not answer this question myself via the command:

$ git describe --contains 7c423e0690

[1] http://llvm.org/git/llvm.git

> The Select_Ri pattern is
> supposed to be lowered into J*_Ri while the latter only support 32-bit
> immediate encoding, therefore Select_Ri should have similar immediate
> predicate check as what J*_Ri are doing.
> 
> Reported-by: Jakub Kicinski <jakub.kicinski@netronome.com>
> Signed-off-by: Jiong Wang <jiong.wang@netronome.com>
> ---
>  lib/Target/BPF/BPFISelLowering.cpp |  8 ++++++--
>  lib/Target/BPF/BPFInstrInfo.td     |  2 +-
>  test/CodeGen/BPF/select_ri.ll      | 35 +++++++++++++++++++++++++++++++++++
>  3 files changed, 42 insertions(+), 3 deletions(-)

-- 
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Principal Kernel Engineer at Red Hat
  LinkedIn: http://www.linkedin.com/in/brouer

  reply	other threads:[~2017-10-12 11:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-12 10:21 [PATCH, bpf-llvm] Fix bug on silently truncating 64-bit immediate Jiong Wang
2017-10-12 11:04 ` Jesper Dangaard Brouer [this message]
2017-10-12 12:08   ` Jiong Wang
2017-10-12 17:11     ` [iovisor-dev] " Y Song

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=20171012130412.72432f87@redhat.com \
    --to=brouer@redhat.com \
    --cc=hans@hanshq.net \
    --cc=iovisor-dev@lists.iovisor.org \
    --cc=jiong.wang@netronome.com \
    --cc=oss-drivers@netronome.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.