From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: 46988@debbugs.gnu.org, larsi@gnus.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: Thu, 23 Jun 2022 19:35:19 +0300 [thread overview]
Message-ID: <831qvfe3so.fsf@gnu.org> (raw)
In-Reply-To: <5AE164C5-3EA7-44CC-8328-448EEA1C50F2@acm.org> (message from Mattias Engdegård on Thu, 23 Jun 2022 18:20:09 +0200)
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Thu, 23 Jun 2022 18:20:09 +0200
> Cc: Pip Cet <pipcet@gmail.com>, larsi@gnus.org, 46988@debbugs.gnu.org,
> monnier@iro.umontreal.ca
>
> 23 juni 2022 kl. 18.08 skrev Eli Zaretskii <eliz@gnu.org>:
>
> > Clang at least attempts to be GCC-compliant. But there are other C
> > compilers we want to support which don't do even that.
>
> Quite true. I don't think we should bother supporting them (at least not right away); just disable the feature for them.
Yes, that's what I meant: we shouldn't break compilation with those,
but we don't have to do more.
prev parent reply other threads:[~2022-06-23 16:35 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
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 [this message]
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=831qvfe3so.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).