From: Thomas Monjalon <thomas@monjalon.net>
To: Akhil Goyal <gakhil@marvell.com>
Cc: Shijith Thotton <sthotton@marvell.com>,
dev@dpdk.org, jerinj@marvell.com, david.marchand@redhat.com
Subject: Re: [dpdk-dev] [pull-request] next-crypto 21.08 rc1
Date: Thu, 08 Jul 2021 09:41:19 +0200 [thread overview]
Message-ID: <2510837.XPcs1ukvDD@thomas> (raw)
In-Reply-To: <2086219.nnIR5hDg31@thomas>
07/07/2021 23:57, Thomas Monjalon:
> 07/07/2021 21:30, Akhil Goyal:
> > Shijith Thotton (2):
> > drivers: add octeontx crypto adapter framework
> > drivers: add octeontx crypto adapter data path
>
> It seems there is an ABI breakage:
>
> devtools/check-abi.sh: line 38: 958581 Segmentation fault
> (core dumped) abidiff $ABIDIFF_OPTIONS $dump $dump2
> Error: ABI issue reported for 'abidiff --suppr devtools/libabigail.abignore --no-added-syms --headers-dir1 v21.05/build-gcc-shared/usr/local/include --headers-dir2 build-gcc-shared/install/usr/local/include v21.05/build-gcc-shared/dump/librte_crypto_octeontx.dump build-gcc-shared/install/dump/librte_crypto_octeontx.dump'
>
> Without this series, the ABI check is passing.
After updating libabigail, it passes OK.
Note there was another bug, in PPC toolchain this time.
After upgrading to recent PPC toolchain it is OK.
What a difficult pull request for the tools!
next prev parent reply other threads:[~2021-07-08 7:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 19:30 [dpdk-dev] [pull-request] next-crypto 21.08 rc1 Akhil Goyal
2021-07-07 21:57 ` Thomas Monjalon
2021-07-08 7:39 ` [dpdk-dev] [EXT] " Akhil Goyal
2021-07-08 7:41 ` Thomas Monjalon [this message]
2021-07-08 7:47 ` [dpdk-dev] " David Marchand
2021-07-08 7:48 ` [dpdk-dev] [EXT] " Akhil Goyal
2021-07-08 17:13 ` [dpdk-dev] " Ali Alnubani
2021-07-08 20:16 ` David Marchand
2021-07-09 4:24 ` [dpdk-dev] [EXT] " Anoob Joseph
2021-07-09 6:43 ` David Marchand
2021-07-09 9:00 ` Anoob Joseph
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=2510837.XPcs1ukvDD@thomas \
--to=thomas@monjalon.net \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=sthotton@marvell.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.