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#46495: 28.0.50; [native-comp] Build fails for 32bit --with-wide-int Date: Wed, 31 Mar 2021 12:16:14 +0000 Message-ID: References: <865z2p0zrq.fsf@gmail.com> <86pn0w59nj.fsf@gmail.com> <83y2eap33a.fsf@gnu.org> <83lfa6kl8s.fsf@gnu.org> <83h7ktlwuy.fsf@gnu.org> <65e12b1d547420e10a19cdad6a33198926abb527.camel@redhat.com> <8335wdknbw.fsf@gnu.org> <83im58k8rb.fsf@gnu.org> <83o8eziw5j.fsf@gnu.org> <83ft0bim95.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="6811"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: andrewjmoreton@gmail.com, dmalcolm@redhat.com, 46495@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Mar 31 14:17:21 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 1lRZmj-0001eV-4z for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 31 Mar 2021 14:17:21 +0200 Original-Received: from localhost ([::1]:58420 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lRZmi-00064J-4t for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 31 Mar 2021 08:17:20 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58398) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lRZmR-000641-2I for bug-gnu-emacs@gnu.org; Wed, 31 Mar 2021 08:17:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:42173) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lRZmQ-0002qb-J2 for bug-gnu-emacs@gnu.org; Wed, 31 Mar 2021 08:17:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lRZmQ-00011g-EI for bug-gnu-emacs@gnu.org; Wed, 31 Mar 2021 08:17: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: Wed, 31 Mar 2021 12:17:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 46495 X-GNU-PR-Package: emacs Original-Received: via spool by 46495-submit@debbugs.gnu.org id=B46495.16171929813876 (code B ref 46495); Wed, 31 Mar 2021 12:17:02 +0000 Original-Received: (at 46495) by debbugs.gnu.org; 31 Mar 2021 12:16:21 +0000 Original-Received: from localhost ([127.0.0.1]:53713 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lRZlk-00010S-NM for submit@debbugs.gnu.org; Wed, 31 Mar 2021 08:16:21 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:55600) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lRZli-00010G-6i for 46495@debbugs.gnu.org; Wed, 31 Mar 2021 08:16:19 -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 12VCGElj005836 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Wed, 31 Mar 2021 12:16:15 GMT In-Reply-To: <83ft0bim95.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 31 Mar 2021 14:41:10 +0300") 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:203349 Archived-At: Eli Zaretskii writes: >> From: Andrea Corallo >> Cc: dmalcolm@redhat.com, andrewjmoreton@gmail.com, 46495@debbugs.gnu.org >> Date: Wed, 31 Mar 2021 08:47:37 +0000 >> >> > AFAIU, this means the libgccjit log file is only output with >> > comp-debug 3 and higher? >> >> Correct, the docstring wasn't correct :/ aa159bf696 should update it to >> reflect the current situation. > > Thanks. > >> > Also, does comp-debug = 3 indeed cause the >> > reproducer to be written, or is that controlled independently by >> > comp-libgccjit-reproducer? >> >> The reproducer is controlled independently by >> `comp-libgccjit-reproducer', the idea behind this is that we want to be >> able to produce reproducers independently from the debug settings (we >> might have a ligccjit bug that is related to one debug option). > > Right, so comp-debug = 3 alone doesn't trigger the reproducer, right? That's correct. >> My proposal would be like: >> >> 0 none >> 1 debug symbols >> 2 debug symbols + pseudo C file >> 3 debug symbols + pseudo C file + GCC passes + libgccjit log file >> >> I think the backtrace issue you are facing is clearly a gdb unwinder >> limitation on Windows that should be fixed in gdb. > > It's more like a missing feature in GDB on platforms that don't use > ELF binary format. I don't hold my breath to have the situation > improved, since this is so far a rare situation when debugging > programs: no one expects debugging code without debug symbols to be > easy. > >> OTOH I understand we can't update gdb for all users that might want >> to help debugging an issue, but I don't like very much the idea to >> have comp-debug 1 as default on every system. What about having 1 >> as default only on Windows? WDYT? > > In general, I'd prefer these settings to be the same on all platforms, > although it isn't a strong feeling in this case. But I'm curious why > you are so against doing that by default on other systems. Can you > explain? Nothing special, just that that as on GNU/Linux we can produce backtraces without debug symbols so seams to me it would be a waste of space to have them always present just for this reason. > Anyway, I've compiled the relevant files with comp-debug = 1, and the > problems with backtraces are now completely gone. So I think we can > more or less close this issue (modulo changing the meanings of > comp-debug and the decision regarding the default value). Sounds good, if my proposal of the new 4 values is acceptable for you and we decide on the default one I can proceed with that. Thanks Andrea