From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 9BAE0385800A for ; Thu, 16 Mar 2023 13:07:53 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 9BAE0385800A Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1678972073; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=tz9us0cxErGRV8JXgluOascT4U1o/TSRHuf6uz9iHDc=; b=eUVVBuP2sPB1yEm1UNeJHaGHdpo1fQt+nj/Wp1JPfjKAupEXSNU2PfYXXh+62MQVrQBq7/ T1bddp8Y5EbENFuwgG5GIb2mrL7Fq1tUMIfBQtxadwGrdeKmm0ROB1RAxA+5oLMN+r4Q5x XzLQgsOj4DV0OBeu/QiQz2/hASm7pnk= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-45-75OKMTGVM_uSLJ_C_tT2eA-1; Thu, 16 Mar 2023 09:07:48 -0400 X-MC-Unique: 75OKMTGVM_uSLJ_C_tT2eA-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id E97472808E6B; Thu, 16 Mar 2023 13:07:46 +0000 (UTC) Received: from tucnak.zalov.cz (unknown [10.39.192.16]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 8DF102166B26; Thu, 16 Mar 2023 13:07:46 +0000 (UTC) Received: from tucnak.zalov.cz (localhost [127.0.0.1]) by tucnak.zalov.cz (8.17.1/8.17.1) with ESMTPS id 32GD7cNx2892743 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Thu, 16 Mar 2023 14:07:38 +0100 Received: (from jakub@localhost) by tucnak.zalov.cz (8.17.1/8.17.1/Submit) id 32GD7ZUK2892742; Thu, 16 Mar 2023 14:07:35 +0100 Date: Thu, 16 Mar 2023 14:07:35 +0100 From: Jakub Jelinek To: Mark Wielaard Cc: Thomas Schwinge , Raiki Tamura , Philip Herron , gcc@gcc.gnu.org, gcc-rust@gcc.gnu.org, David Edelsohn , Arthur Cohen , Arsen =?utf-8?Q?Arsenovi=C4=87?= Subject: Re: [GSoC] gccrs Unicode support Message-ID: Reply-To: Jakub Jelinek References: <87lejxujso.fsf@euler.schwinge.homeip.net> MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 3.1 on 10.11.54.6 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-3.7 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Thu, Mar 16, 2023 at 01:58:57PM +0100, Mark Wielaard wrote: > On Thu, 2023-03-16 at 10:28 +0100, Thomas Schwinge wrote: > > I'm now also putting Mark Wielaard in CC; he once also started discussing > > this topic, "thinking of importing a couple of gnulib modules to help > > with UTF-8 processing [unless] other gcc frontends handle [these things] > > already in a way that might be reusable".  See the thread starting at > > > > "rust frontend and UTF-8/unicode processing/properties". > > Thanks. BTW. I am not currently working on this. > Note the responses in the above thread by Ian and Jason who pointed out > that some of the requirements of the gccrs frontend might be covered in > the go frontend and libcpp, but not really in a reusable way. libcpp can be certainly linked into the gccrs FE and specific functions called from it even if libcpp isn't used as a preprocessor for the language. Small changes to libcpp are obviously possible as well to make it work. Jakub