Skip to content

[NO REVIEW] Repair assertions for LFortran - #353

Merged
bonachea merged 2 commits into
BerkeleyLab:mainfrom
bonachea:lfortran-assert
Jul 31, 2026
Merged

[NO REVIEW] Repair assertions for LFortran#353
bonachea merged 2 commits into
BerkeleyLab:mainfrom
bonachea:lfortran-assert

Conversation

@bonachea

Copy link
Copy Markdown
Member

The assertion failure path for LFortran was previously hitting a segmentation fault (with no output). Consequently Caffeine's many assertion checks were not being correctly reported when triggered under LFortran.

Deploy fixes and workaround to ensure high-quality assertion failure output with LFortran.

CC: @Jainam-not-a-robot

bonachea added 2 commits July 30, 2026 16:04
This picks up a critical improvement for LFortran 0.60 and later,
to ensure preprocessor-rendered assertion expressions appear in
the assertion message output.
The assert_callback_error_stop makes a bind(C) call to caf_fatal_error,
which is currently miscompiled by LFortran, resulting in a segmentation fault
(which fails to output the assertion information).

Replace with a bare invocation of `error stop` for LFortran, as
a temporary workaround until the compiler defect is repaired
@bonachea
bonachea merged commit 581e315 into BerkeleyLab:main Jul 31, 2026
55 checks passed
@bonachea
bonachea deleted the lfortran-assert branch July 31, 2026 00:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant