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#46256: [feature/native-comp] AOT eln files ignored if run from build tree Date: Sat, 06 Mar 2021 18:30:05 +0000 Message-ID: References: <861rd1tbpa.fsf@gmail.com> <83pn0km6y3.fsf@gnu.org> <86ft1f8ara.fsf@gmail.com> <83sg5cjdn8.fsf@gnu.org> <83r1kwjcy2.fsf@gnu.org> <83k0qoj9zv.fsf@gnu.org> <83im68j963.fsf@gnu.org> <83tuprhur0.fsf@gnu.org> <83o8fxyafx.fsf@gnu.org> <83h7lpy7b7.fsf@gnu.org> <83blbxxwuj.fsf@gnu.org> <83a6rgwdmr.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="19169"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: 46256@debbugs.gnu.org, andrewjmoreton@gmail.com To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Mar 06 19:31:18 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 1lIbhu-0004vY-BB for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 06 Mar 2021 19:31:18 +0100 Original-Received: from localhost ([::1]:43796 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lIbhs-0004Lc-Rl for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 06 Mar 2021 13:31:16 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59082) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lIbhe-0004LR-TK for bug-gnu-emacs@gnu.org; Sat, 06 Mar 2021 13:31:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:54969) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lIbhe-0001ho-65 for bug-gnu-emacs@gnu.org; Sat, 06 Mar 2021 13:31:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lIbhe-0004fL-1D for bug-gnu-emacs@gnu.org; Sat, 06 Mar 2021 13:31:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Andrea Corallo Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 06 Mar 2021 18:31:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 46256 X-GNU-PR-Package: emacs Original-Received: via spool by 46256-submit@debbugs.gnu.org id=B46256.161505541017870 (code B ref 46256); Sat, 06 Mar 2021 18:31:01 +0000 Original-Received: (at 46256) by debbugs.gnu.org; 6 Mar 2021 18:30:10 +0000 Original-Received: from localhost ([127.0.0.1]:38281 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lIbgo-0004e9-7D for submit@debbugs.gnu.org; Sat, 06 Mar 2021 13:30:10 -0500 Original-Received: from mx.sdf.org ([205.166.94.24]:61744) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lIbgl-0004cy-5q for 46256@debbugs.gnu.org; Sat, 06 Mar 2021 13:30:08 -0500 Original-Received: from mab (ma.sdf.org [205.166.94.33]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 126IU5h0005583 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Sat, 6 Mar 2021 18:30:05 GMT In-Reply-To: <83a6rgwdmr.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 06 Mar 2021 16:38:52 +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:201656 Archived-At: Eli Zaretskii writes: >> From: Andrea Corallo >> Cc: 46256@debbugs.gnu.org, andrewjmoreton@gmail.com >> Date: Fri, 05 Mar 2021 19:22:34 +0000 >> >> What we have as a doc is directly in the docstring of >> `comp-libgccjit-reproducer', I guess we could improve it. >> >> Essentially having it bound to t while compiling produces a C file >> deposed where the .eln target directory. > > The reproducer file is attached. It is large, so I compressed it. > Let me know if you see there anything that could explain the problem. > >> This file ELNFILENAME_libgccjit_repro.c can be just compiled linking >> against libgccjit to obtain the reproducer. > > "To obtain the reproducer" meaning that the compiled and linked > program should crash in the same way is Emacs does? I thought we > crash while compiling the file and linking it to produce a shared > library, not while running it. Right? Yes, the compiled program when executed will replay the same compilation attempted by Emacs and therefore if is a libgccjit fault it should crash. Does the reproducer crash when executed on your system? >> libgccjit should never segfault so if this crashes is clearly a bug. > > Let's see what you can find in the reproducer file. Thanks, I'm going to have a look if I can reproduce here. > Meanwhile, I see that: > > . the file has DOS CRLF end-of-line format, because libgccjit opens > the reproducer file in the default text mode > . the file includes control characters: ^A, ^B, ^M, and others -- > what are those for? I hope we cannot have ^Z there, because AFAIK > text-mode writes will stop at the first such byte > > More generally, what is the relation between the contents of the > reproducer file and the source the native compilation sees when we > call gcc_jit_context_compile_to_file? Do we submit a similar file to > GCC or something? The reproducer file is a file that is meant to recreate the same libgccjit IR and attempt a compilation with that. In practice it calls the same functions we call at the interface with libgccjit describing the code we want to compile and attempt to perform a compilation. > IOW, can any weird characters I see in the > reproducer be relevant to the actual compilation (and thus to the > crash)? I'm not sure why these characters are there but I don't think they are relevant to the crash. Thanks! Andrea