From: Anthony Martin <ality@pbrane.org>
To: 9front@9front.org
Subject: [9front] commit 68b4a8e6ef5ca0d26bc026f69acddb76600197ac
Date: Tue, 18 Jun 2024 04:28:26 -0700 [thread overview]
Message-ID: <ZnFvWhJ-cnxuYQfB@alice> (raw)
I enjoy multiple decades-old bugs. Good find.
In 2e there was no TINT. Instead lex.c:/^cinit had this:
tint = types[TLONG]; /* assuming long, ginit knows */
tuint = types[TULONG];
Ken fat-fingered (or sam-stumbled?) the refactor when
the dpcheck/varargck code was added to brazil.
I imagine they'll let it slide during the canonization.
Cheers,
Anthony
reply other threads:[~2024-06-18 11:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ZnFvWhJ-cnxuYQfB@alice \
--to=ality@pbrane.org \
--cc=9front@9front.org \
/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.
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 NNTP newsgroup(s).