Codegen fails with large real literals

[timmw]

Issue Description

When attempting to use a large real number gte 2989000001.0 jank produces an error:

user=> (float 2989000000.0) ; works
2.989e+09

user=> (float 2989000001.0) ; breaks
In file included from <<< inputs >>>:1:
input_line_5:3:15: error: call to constructor of 'jank::runtime::obj::small_real_ref' (aka 'oref<small_real>') is ambiguous
    3 | auto const v0(jank::runtime::obj::small_real_ref{ 2989000001 });
      |               ^                                 ~~~~~~~~~~~~~~
/home/tim/src/third-party/jank/compiler+runtime/include/cpp/jank/runtime/oref.hpp:1784:5: note: candidate constructor
 1784 |     oref(int const data) noexcept
      |     ^
/home/tim/src/third-party/jank/compiler+runtime/include/cpp/jank/runtime/oref.hpp:1789:5: note: candidate constructor
 1789 |     oref(f64 const data) noexcept
      |     ^
error: Parsing failed.
─ internal/codegen-failure ─────────────────────────────────────────────────────────────────────────
error: Unable to compile C++ source.

Unsure if all bets are off once the above is triggered but it leads to subsequent JIT session errors:

user=> (float 1.0)
JIT session error: Symbols not found: [ _ZN4jank7runtime8make_boxIdQsr3stdE19is_floating_point_vIT_EEENS0_4orefINS0_3obj10small_realEEES2_ ]
─ internal/failure ─────────────────────────────────────────────────────────────────────────────────
error: Failed to find symbol: 'user_cpp_call_4_0'


Stack trace (most recent call first):
#0  in jank::error::internal_failure(jtl::immutable_string const&) at jank
#1  in jank::error::throw_internal_failure(jtl::immutable_string const&) at jank
#2  in void jtl::detail::panic<jtl::result<void*, jtl::immutable_string> >(jtl::result<void*, jtl::immutable_string> const&) at jank
#3  in jank::jit::processor::create_function(unsigned char, jtl::immutable_string const&, folly::fbvector<unsigned char, gc_allocator<unsigned char> > const&, bool) const at jank
#4  in jank::runtime::obj::deferred_cpp_function::realize() const at jank
#5  in jank::runtime::obj::deferred_cpp_function::call() const at jank
#6  in jank::evaluate::eval(jtl::ref<jank::analyze::expr::cpp_call>) at jank
#7  in jank::evaluate::eval(jtl::ref<jank::analyze::expression>) at jank
#8  in jank::runtime::context::eval_string(jtl::immutable_string const&, jank::read::source_position const&) const at jank
#9  in jank::runtime::context::eval_file(jtl::immutable_string const&) at jank
#10 in main::$_0::operator()(int, char const**) const at jank
#11 in jank_init_dynamic at jank

I've omitted this stack trace from the dedicated field as it's separate to the initial bug being reported.

Reproduction Steps

Eval this in repl:

(float 2989000001.0)

jank health check

─ system ──────────────────────────────────────────────────────────────────────
─ ✅ operating system: linux
─ ✅ default triple: x86_64-unknown-linux-gnu

─ jank install ────────────────────────────────────────────────────────────────
─ ✅ jank version: jank-0.1-alpha
─ ✅ jank resource dir: ../lib/jank/0.1
─ ✅ jank resolved resource dir: /home/tim/.local/bin/../lib/jank/0.1 (found)
─ ✅ jank user cache dir: /home/tim/.cache/jank/x86_64-unknown-linux-gnu-c89264ae995a47f2555460e0b3253b579bc1aa3c3ac6435e57f6d6a107541d20 (found)

─ clang install ───────────────────────────────────────────────────────────────
─ ✅ configured clang path: /nix/store/9g5ba0n1q617mcbqk8y1lcwzlsdvdknl-clang-wrapper-22.1.2/bin/clang++ (found)
─ ✅ configured clang resource dir: /nix/store/9g5ba0n1q617mcbqk8y1lcwzlsdvdknl-clang-wrapper-22.1.2/resource-root (found)

─ jank runtime ────────────────────────────────────────────────────────────────
─ ✅ jank runtime initialized
─ ✅ jank pch path: /home/tim/.cache/jank/x86_64-unknown-linux-gnu-c89264ae995a47f2555460e0b3253b579bc1aa3c3ac6435e57f6d6a107541d20 (found)
─ ✅ jank can jit compile c++
─ ✅ jank can aot compile working binaries

─ support ─────────────────────────────────────────────────────────────────────
If you're having issues with jank, please either ask the jank community on the Clojurians Slack or report the issue on Github.

─ Slack: https://clojurians.slack.com/archives/C03SRH97FDK
─ Github: https://github.com/jank-lang/jank

Stack trace

No response

OS Version Information

Fedora 43

I acknowledge that:

• I have searched the jank repository (both open and closed Discussions and Issues) and confirm this is not a duplicate of an existing issue or discussion.
• I have checked the "Preview" tab on all text fields to ensure that everything looks right, and have wrapped all configuration and code in code blocks with a group of three backticks (```) on separate lines.

[jeaye]

Thank you for another excellent report with a simple repro. This is now fixed and tested: #834