From: Kevin Buettner <kevinb@redhat.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/testsuite] Fix pi approximation
Date: Mon, 2 Feb 2026 10:29:48 -0700 [thread overview]
Message-ID: <20260202102948.29e284b6@f42-mesa-1> (raw)
In-Reply-To: <20260126124112.1400069-1-tdevries@suse.de>
On Mon, 26 Jan 2026 13:41:12 +0100
Tom de Vries <tdevries@suse.de> wrote:
> From: Tom de Vries <tdevries@suse.de>
> To: gdb-patches@sourceware.org
> Subject: [PATCH] [gdb/testsuite] Fix pi approximation
> Date: Mon, 26 Jan 2026 13:41:12 +0100
>
> In gdb.dap/ada-non-ascii/prog.adb, I came across the following:
> ...
> __ : Integer := 3; -- The Indiana Approximation.
> ...
>
> This article [1] explains the background behind the comment: the Indiana
> pi bill.
>
> Given that the common interpretation seems to be that the bill implies
> that __ == 3.2 [2]:
> ...
> The bill ... has been claimed to imply a number of different values for
> __, although the closest it comes to explicitly asserting one is the
> wording "the ratio of the diameter and circumference is as five-fourths
> to four", which would make __ = 16___5 = 3.2, ... .
> ...
> change the type to float, and set it to 3.2.
>
> Luckily, in this particular case, changing the approximation of __ has no
> effect, so the test-case still passes :) .
>
> Tested on x86_64-linux.
>
> [1] https://en.wikipedia.org/wiki/Indiana_pi_bill
> [2] https://en.wikipedia.org/wiki/Approximations_of_pi#Indiana_bill
I had, of course, heard of this, but I did not realize that the
approximation was 3.2 instead of 3. But since we strive for
historical accuracy in all of our testing ;) ...
Approved-by: Kevin Buettner <kevinb@redhat.com>
prev parent reply other threads:[~2026-02-02 17:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 12:41 Tom de Vries
2026-02-02 17:29 ` Kevin Buettner [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260202102948.29e284b6@f42-mesa-1 \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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