Skip to content

LIBASR Sync #2860

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 18 commits into from
Jul 10, 2025
Merged

LIBASR Sync #2860

merged 18 commits into from
Jul 10, 2025

Conversation

swamishiju
Copy link
Collaborator

No description provided.

@certik
Copy link
Contributor

certik commented Jul 7, 2025

The failures like:

/home/runner/work/lpython/lpython/lpython-0.22.0-147-g349c9b2e9/src/lpython/python_kernel.cpp:83:32: error: ‘struct LCompilers::CompilerOptions’ has no member named ‘generate_object_code’
   83 |             e.compiler_options.generate_object_code = false;
      |                                ^~~~~~~~~~~~~~~~~~~~

Are easy to fix --- it's now called "separate_compilation".

@certik
Copy link
Contributor

certik commented Jul 8, 2025

Go ahead and use libasr from LFortran master.

@certik
Copy link
Contributor

certik commented Jul 10, 2025

Go ahead and use the master of LFortran. Then I'll do a final review and let's merge it.

Copy link
Contributor

@certik certik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that this is good.

@certik certik merged commit c447fca into lcompilers:main Jul 10, 2025
18 checks passed
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.

2 participants