From nobody Mon May 30 18:44:58 2022 X-Original-To: riscv@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 72A5B1B500E0 for ; Mon, 30 May 2022 18:45:42 +0000 (UTC) (envelope-from dclarke@blastwave.org) Received: from mail.oetec.com (mail.oetec.com [108.160.241.186]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.oetec.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4LBkr52SRXz3LrV for ; Mon, 30 May 2022 18:45:38 +0000 (UTC) (envelope-from dclarke@blastwave.org) X-Spam-Status: No X-oetec-MailScanner-From: dclarke@blastwave.org X-oetec-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-3.585, required 6, autolearn=not spam, ALL_TRUSTED -1.00, BAYES_00 -1.90, DKIM_SIGNED 0.10, DKIM_VALID -0.10, DKIM_VALID_AU -0.10, DKIM_VALID_EF -0.10, NICE_REPLY_A -0.48, T_SCC_BODY_TEXT_LINE -0.01, URIBL_BLOCKED 0.00) X-oetec-MailScanner: Found to be clean X-oetec-MailScanner-ID: 24UIiw8D002413 X-oetec-MailScanner-Information: Please contact oetec for more information Received: from [10.14.0.4] (static-198-54-132-53.cust.tzulo.com [198.54.132.53]) (authenticated bits=0) by mail.oetec.com (8.15.2/8.15.2/Debian-8+deb9u1) with ESMTPSA id 24UIiw8D002413 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Mon, 30 May 2022 14:45:00 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=blastwave.org; s=default; t=1653936300; bh=n1ilHEdIWx3S2vtzobsqhGz/s95lNQ8e70MQ5x3qMqA=; h=Date:Subject:To:References:From:In-Reply-To:From; b=mVKhFFmmLvljiKibdpHYbBFLzouNglUzBGatnolEaKmLaPbrhef18SgWIhIIwlB+i tgAt9pYslzi8zKuo1GN/LiZzwqxD4X4t4SI5e06F36umWB8cRdHTLN3+WDhj0S29+R sUdRd0tXeCsPpwPaaaEE91LqgMpTiPIwGQWj9VQpuxQ0xvarEGEujpSj1XuP+b4uFm 8HeC9rNhfQBs3rvcV6r6JXyldNGw/KwS3DgGOgtQurWfJ2oWtucqW1ByhZmnMJNuwX H4JU9oPMCtBeVrK3CfY1ex/9M30EV1DOWuFRXXv1p5gUdF4gSN7eRnUcGl4S+MHo+O h6HgaJoFdQHwQ== Message-ID: Date: Mon, 30 May 2022 14:44:58 -0400 List-Id: FreeBSD on the RISC-V instruction set architecture List-Archive: https://lists.freebsd.org/archives/freebsd-riscv List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-riscv@freebsd.org X-BeenThere: freebsd-riscv@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 Subject: Re: Is there no working clang in FreeBSD/RISC-V's ports? Content-Language: en-US To: riscv@freebsd.org References: <2AE7AF78-729F-4D6B-AF62-9A79703343D8@hamburg.de> From: Dennis Clarke In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4LBkr52SRXz3LrV X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=blastwave.org header.s=default header.b=mVKhFFmm; dmarc=pass (policy=quarantine) header.from=blastwave.org; spf=pass (mx1.freebsd.org: domain of dclarke@blastwave.org designates 108.160.241.186 as permitted sender) smtp.mailfrom=dclarke@blastwave.org X-Spamd-Result: default: False [-3.70 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[blastwave.org:s=default]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[riscv@freebsd.org]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; RCVD_IN_DNSWL_MED(-0.20)[108.160.241.186:from]; DKIM_TRACE(0.00)[blastwave.org:+]; DMARC_POLICY_ALLOW(-0.50)[blastwave.org,quarantine]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MLMMJ_DEST(0.00)[riscv]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:812, ipnet:108.160.240.0/20, country:CA]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On 5/27/22 18:21, Jessica Clarke wrote: > On 27 May 2022, at 22:41, lars.sonchocky-helldorf@hamburg.de wrote: >> . . . > That’s just a freshports data gathering issue, it doesn’t know the > riscv64 package sets exist so doesn’t report on them. I’ve filed > https://github.com/FreshPorts/freshports/issues/364 for this. > >> Quote from https://docs.freebsd.org/en/articles/committers-guide/#archs >> >> • Tier 2 platforms should be self-hosting either via... >> >> doesn’t specifically that mean that the llvm-devel port should be available? Just asking … > > RISC-V is self-hosting via the in-tree toolchain, thus no external > toolchain is required, and thus no official binary packages are > required to be provided. Out of the box you can compile with Clang and > link with LLD, no packages needed. You only need the packages if you > need a different specific version or you need to use libLLVM/libClang’s > APIs. > > Jess > Has something changed in the last three weeks? I see ver 13.0.0 here : ison$ uname -apKU FreeBSD ison 14.0-CURRENT FreeBSD 14.0-CURRENT #2 main-n255202-0aef8628458-dirty: Sun May 8 20:33:55 UTC 2022 root@ison:/usr/obj/usr/src/riscv.riscv64/sys/GENERIC riscv riscv64 1400057 1400057 ison$ ison$ cc --version FreeBSD clang version 13.0.0 (git@github.com:llvm/llvm-project.git llvmorg-13.0.0-0-gd7b669b3a303) Target: riscv64-unknown-freebsd14.0 Thread model: posix InstalledDir: /usr/bin ison$ Which may be a valid reason to fire off a buildworld etc but I see no issues with whatever was clang a few weeks ago. -- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX and Linux spoken GreyBeard and suspenders optional