[dpdk-dev] [PATCH v2] eal/windows: export all built functions for clang

Tal Shnaiderman talshn at nvidia.com
Wed Oct 7 16:14:07 CEST 2020


>> Subject: [dpdk-dev] [PATCH v2] eal/windows: export all built functions for
>> clang
>>  
>>  CAUTION: This email originated from outside of the organization. Do not click
>>  links or open attachments unless you recognize the sender and know the
>>  content is safe.
>>  
>>  export for clang build all the functions currently built on Windows and listed
>>  in rte_eal_version.map by adding them to rte_eal_exports.def.
>>  
>>  Signed-off-by: Tal Shnaiderman <mailto:talshn at nvidia.com>
>>  Acked-by: Ranjit Menon <mailto:ranjit.menon at intel.com>
>>  ---
>>  v2: rebase to master
>>  ---
>>  ---
>>  lib/librte_eal/rte_eal_exports.def | 156
>>  +++++++++++++++++++++++++++++++++++--
>>  1 file changed, 151 insertions(+), 5 deletions(-)
>>  
> Are we close to being able to drop the custom .def file for the Windows EAL and use the one generated from the .map file as with the other RTE libraries? How many functions are undefined now in the Windows EAL?

Hi John,

We're missing 77 additional functions exported in the map file for Linux, many I assume are related to the missing interrupts implementation, however some are unneeded by Windows (e.g. all the rte_vfio_* exports).

Regarding dropping the .def file completely, Harini, do you have an estimation when this task will be completed? 


More information about the dev mailing list