Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 684800 - dev-libs/beignet deprecation
Summary: dev-libs/beignet deprecation
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Marek Szuba (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-30 13:19 UTC by David Heidelberg (okias)
Modified: 2019-06-13 11:58 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Heidelberg (okias) 2019-04-30 13:19:48 UTC
Since it requires old LLVM6 and superseded by Intel NEO, I think this package should be marked as deprecated.
Comment 1 Marek Szuba (RETIRED) archtester gentoo-dev 2019-04-30 14:46:23 UTC
I will deprecate it once we have actually got NEO in the tree. In the meantime, let's leave it be - especially given "old" LLVM6 is in fact the latest stable release for now.
Comment 2 Timo Ollech 2019-05-16 17:10:38 UTC
The stable version beignet-1.3.2 even depends on LLVM 5 -

<sys-devel/clang-6.0.0:=[${MULTILIB_USEDEP}]

But on the other hand Intel's website says

"Beignet remains our recommended solution for legacy HW platforms (e.g. Ivybridge, Sandybridge, Haswell)."

So what to do with it?
Comment 3 Marek Szuba (RETIRED) archtester gentoo-dev 2019-05-17 09:46:17 UTC
Okay, I was going to comment on this earlier but I forgot. This is the way I see it:
 - dev-libs/beignet will remain available in Gentoo for as long as it works and does not force us to keep broken or EOLed dependencies in the tree. I know for a fact people still work on machines with CPUs not supported by Neo (if they work and are sufficient for someone's needs, why not? I for one have got a high-end Ivy Bridge system which I still use from time to time for heavy-duty number crunching. BTW. This reminds me of old 486 Linux boxes being used to effortlessly run production servers in the 1990 long after Microsoft had given up on those CPUs) and would have to leave such people out in the cold unless there are very, very good reasons for that;
 - latest Beignet ebuilds do support LLVM6, moreover while there haven't been any commits to Beignet master since August 2018 the devs *have* added preliminary LLVM7 support. To put it another way, chances are pretty good that it depending on EOLed LLVM will not be Beignet's problem any time soon.

I hoped Beignet upstream would make one more release but alas, it hasn't happened yet. Now that llvm.eclass is about to gain EAPI-7 support I think it's time to stop waiting - I'll poke them about it on the mailing list but regardless of the result, my plan is to add dev-libs/beignet-1.3.3(_pre2019xxxx)? to the tree once it can use EAPI 7, stabilise it after the usual maturation period, and officially declare Beignet in Gentoo to become a maintenance-only package.

As for Neo, it should definitely be added to virtual/opencl but I want to let it sit in the tree for a while before doing so lest some unexpected bugs pop up.
Comment 4 Marek Szuba (RETIRED) archtester gentoo-dev 2019-06-13 11:58:26 UTC
Status update:
 - NEO doesn't support all the hardware Beignet does, nor does it support ABI_x86_32. Therefore, dev-libs/beignet isn't going anywhere any time soon;
 - that said, in 64-bit mode and on supported hardware NEO seems to work fine where it can so I have just requested virtual/opencl to include it.