From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Gerd Moellmann <gerd@gnu.org>, 75451-done@debbugs.gnu.org
Subject: bug#75451: scratch/igc: Enable CHECK_STRUCTS
Date: Thu, 09 Jan 2025 08:25:07 +0100 [thread overview]
Message-ID: <m2r05co3e4.fsf@gmail.com> (raw)
In-Reply-To: <CADwFkmkV+7Lrb5e83_Tb6mCxDP85cZE1sm3OMEzO_M0=bvAnAw@mail.gmail.com> (Stefan Kangas's message of "Thu, 9 Jan 2025 01:20:38 -0600")
Stefan Kangas <stefankangas@gmail.com> writes:
>
>> (BTW, the contents of the #if might be out of date, not sure if we
>> meanwhile fix/scan additional structs.)
>
> I've now added checks for all structs that we use in "fix_*" functions
> (commit 76a0d739024). I kept notes to make sure I didn't miss anything,
> but it's not impossible that I did. I'll double-check things later.
>
> I plan to do anything passed to the "finalize_*" ones next, which should
> cover most of the ones we currently depend on, I think.
Very nice! Thanks for taking this on!
next prev parent reply other threads:[~2025-01-09 7:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 3:57 bug#75451: scratch/igc: Enable CHECK_STRUCTS Stefan Kangas
2025-01-09 5:09 ` Gerd Möllmann
2025-01-09 7:20 ` Stefan Kangas
2025-01-09 7:25 ` Gerd Möllmann [this message]
2025-01-09 10:09 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-09 12:44 ` Stefan Kangas
2025-01-16 14:38 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-17 16:36 ` Stefan Kangas
2025-01-17 16:51 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-17 20:48 ` Eli Zaretskii
2025-01-10 18:42 ` Stefan Kangas
2025-01-10 18:58 ` Gerd Möllmann
2025-01-10 19:33 ` Paul Eggert
2025-01-20 2:01 ` Stefan Kangas
2025-01-20 3:32 ` Gerd Möllmann
2025-01-20 5:03 ` Paul Eggert
[not found] ` <87ed0xykig.fsf@protonmail.com>
2025-01-20 20:23 ` Stefan Kangas
[not found] ` <87jzaqx72v.fsf@protonmail.com>
2025-01-20 17:54 ` Stefan Kangas
2025-01-20 20:25 ` Paul Eggert
2025-01-20 20:32 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-10 19:56 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-10 23:14 ` Paul Eggert
2025-01-14 15:22 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-14 19:24 ` Paul Eggert
2025-01-14 21:43 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-17 14:46 ` Andrea Corallo
2025-01-17 19:50 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2r05co3e4.fsf@gmail.com \
--to=gerd.moellmann@gmail.com \
--cc=75451-done@debbugs.gnu.org \
--cc=gerd@gnu.org \
--cc=stefankangas@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.