From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 082AB158095 for ; Mon, 8 Aug 2022 16:44:35 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0C5532BC01A; Mon, 8 Aug 2022 16:44:34 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id DCE412BC01A for ; Mon, 8 Aug 2022 16:44:33 +0000 (UTC) Received: from [2a0c:b641:69c:e7f1::2] (port=34194 helo=aurora) by muon with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1oL5ri-0001KJ-4V for gentoo-soc@lists.gentoo.org; Mon, 08 Aug 2022 16:44:30 +0000 From: Benda Xu To: gentoo-soc Subject: Re: [gentoo-soc] Week 8 Report for Refining ROCm Packages in Gentoo References: Date: Tue, 09 Aug 2022 00:44:24 +0800 In-Reply-To: (wuyy's message of "Mon, 8 Aug 2022 23:15:59 +0800") Message-ID: <878rnyit1z.fsf@gentoo.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-soc@lists.gentoo.org Reply-to: gentoo-soc@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: text/plain X-Archives-Salt: aeb7e976-d30d-436e-9ac5-fd288ca18f78 X-Archives-Hash: 70993ed2458fd3025ed4df2b18f2ce71 wuyy writes: > I'm back on GSoC after a two-week temporary leave. > > This week there are two major progress: dev-util/rocprofiler and > rocm.eclass. > > I have implemented all the functions I think necessary for rocm.eclass. > It was just send to rocm.eclass draft to gentoo-dev mailing list (also > with a Github PR at [1]), please have a review. In the following weeks, > I will collect feedbacks and continue to polish it. > > In summary, I have implemented those functions which is listed in my > proposal: > - USE_EXPNAD of amdgpu_targets_, and ROCM_USEDEP to make the use flag > coherent among dependencies; > - rocm_src_configure contains common arguments in src_prepare; > - rocm_src_test which checks the permission on /dev/kfd and > /dev/dri/render* > > [...] > > Actually I have never imagined rocm.eclass could be in this shape > eventually. Initially I just thought it would provide some utilities, > mainly src_test and USE_EXPAND. But when implementing I found all these > feature requires careful treatment. The comments (mainly examples) also > takes half of the length. It ends up in 278 lines, which is a > middle-sized among current eclasses. Maybe it can be further trimmed > down after polishing, because there could be awkward implementations or > re-inventions in it. > > Based on my draft rocm.eclass, I have prepared sci-libs/roc*=5.1.3, > sci-lib/hip-*-5.1.3 and dev-python/cupy making use of it. It feels great > to simplify the ebuilds, and portage can handles the USE_EXPAND and > dependencies just as expected. Once the rocm.eclass get in tree, I'll > push those ROCm-5.1.3 ebuilds. > > [...] > > According to the renewed proposal (I have been leaving for two weeks, > so there are changes in plan), I should collect feedback and refine > rocm.eclass, and prepare dev-python/cupy and sci-libs/rocWMMA. I'll > investigate ROCgdb, too. Also, rocm-device-libs is a major package > because many users relies on it to provide opencl. I'll work on > bumping its version, too. What's more, with hip-5.1.3 against vanilla > clang, rocm for blender can land in ::gentoo. Nice progress! We will put the eclass the highest priority. Benda