From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#43725: 28.0.50; Include feature/native-comp into master Date: Mon, 15 Mar 2021 15:43:07 +0000 Message-ID: References: <83a6s04glg.fsf@gnu.org> <83k0qzv54q.fsf@gnu.org> <83lfawp2cc.fsf@gnu.org> <83k0qgp0hj.fsf@gnu.org> <837dmfp2x7.fsf@gnu.org> <83v99znizq.fsf@gnu.org> <83o8frnf2r.fsf@gnu.org> <83r1khfy5d.fsf@gnu.org> <83k0q9fr91.fsf@gnu.org> <838s6ofnr7.fsf@gnu.org> Reply-To: Andrea Corallo Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27402"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: larsi@gnus.org, monnier@iro.umontreal.ca, 43725@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Mar 15 16:47:16 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lLpR6-0006yi-FC for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 15 Mar 2021 16:47:16 +0100 Original-Received: from localhost ([::1]:36330 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lLpR5-00028d-Fi for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 15 Mar 2021 11:47:15 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46832) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lLpNz-00082D-3E for bug-gnu-emacs@gnu.org; Mon, 15 Mar 2021 11:44:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:53103) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lLpNy-0007gJ-QK for bug-gnu-emacs@gnu.org; Mon, 15 Mar 2021 11:44:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lLpNy-0006jd-MJ for bug-gnu-emacs@gnu.org; Mon, 15 Mar 2021 11:44:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Andrea Corallo Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 15 Mar 2021 15:44:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 43725 X-GNU-PR-Package: emacs Original-Received: via spool by 43725-submit@debbugs.gnu.org id=B43725.161582299425770 (code B ref 43725); Mon, 15 Mar 2021 15:44:02 +0000 Original-Received: (at 43725) by debbugs.gnu.org; 15 Mar 2021 15:43:14 +0000 Original-Received: from localhost ([127.0.0.1]:36405 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lLpNC-0006ha-Je for submit@debbugs.gnu.org; Mon, 15 Mar 2021 11:43:14 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:56311) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lLpN8-0006hL-R6 for 43725@debbugs.gnu.org; Mon, 15 Mar 2021 11:43:13 -0400 Original-Received: from mab (ma.sdf.org [205.166.94.33]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 12FFh7t4028128 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Mon, 15 Mar 2021 15:43:08 GMT In-Reply-To: <838s6ofnr7.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 15 Mar 2021 17:19:24 +0200") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:202409 Archived-At: Eli Zaretskii writes: > One issue that I have in my notes about native-comp is the issue with > input encoding of the source we submit to the native-compiler. > > The issue is this: our Lisp files are generally encoded in UTF-8. But > there's no guarantee that GCC expects the source to be encoded in > UTF-8. If the text we submit to libgccjit for compilation is in the > same encoding as the original .el files, then shouldn't we tell GCC > its actual encoding, to make sure non-ASCII text aren't mangled? The only generated text we are passing to libgccjit is feed to 'gcc_jit_context_new_string_literal'. This text is generated from 'Fprin1_to_string' that we use to essentially render in form of text immediate objects. I thought this was disconnected from the encoding of the source file, am I wrong? Thanks Andrea