From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 46988@debbugs.gnu.org, mattiase@acm.org,
monnier@iro.umontreal.ca, pipcet@gmail.com
Subject: bug#46988: 28.0.50; Documenting and verifying assumptions about C code not calling quit or GCing
Date: Mon, 20 Jun 2022 14:47:48 +0300 [thread overview]
Message-ID: <83a6a7mu8r.fsf@gnu.org> (raw)
In-Reply-To: <87zgi8p0vd.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon, 20 Jun 2022 03:41:42 +0200)
> Cc: 46988@debbugs.gnu.org,
> Mattias Engdegård <mattiase@acm.org>,
> Stefan Monnier <monnier@iro.umontreal.ca>
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Mon, 20 Jun 2022 03:41:42 +0200
>
> Pip Cet <pipcet@gmail.com> writes:
>
> > Patch attached. It assumes the standard stack growth direction, and
> > that __builtin_frame_address (0) is available and works. Uses GCC's
> > __attribute__ ((cleanup (...))).
> >
> > My point here is that the technical implementation isn't the problem,
> > the question is whether we're disciplined enough to run with checking
> > enabled and react to bug reports about the fatal error being thrown.
>
> I've respun the patch for the current trunk, and I wonder whether
> anybody has any comments here (so I've added Stefan and Mattias to the
> CCs).
>
> I think if we add this, it should be enabled only if the build is
> configured with --enable-checking.
Yes, I agree.
In addition, AFAIU this uses some GCC-specific stuff without providing
for other compilers that don't support the same literal features.
next prev parent reply other threads:[~2022-06-20 11:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 13:47 bug#46988: 28.0.50; Documenting and verifying assumptions about C code not calling quit or GCing Pip Cet
2021-03-07 14:06 ` Pip Cet
2021-03-08 19:42 ` Lars Ingebrigtsen
2021-03-08 19:57 ` Pip Cet
2021-03-09 14:05 ` Lars Ingebrigtsen
2021-03-10 18:28 ` Matt Armstrong
2021-03-10 19:09 ` Pip Cet
2021-03-11 23:17 ` Matt Armstrong
2022-06-20 1:41 ` Lars Ingebrigtsen
2022-06-20 11:47 ` Eli Zaretskii [this message]
2022-06-23 15:56 ` Pip Cet
2022-06-23 16:08 ` Eli Zaretskii
2022-06-23 16:20 ` Mattias Engdegård
2022-06-23 16:35 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83a6a7mu8r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46988@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mattiase@acm.org \
--cc=monnier@iro.umontreal.ca \
--cc=pipcet@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).