[f2dace/dev, fortran] 1) Consolidate global data objects into a single struct, 2) Then pass it around in the processed AST as function arguments, 3) Try to keep the global data serialisation and deserialisation in sync. #1951

pratyai · 2025-02-24T18:07:28Z

No description provided.

pratyai · 2025-02-24T20:58:06Z

handler integer itself), so we can const propagate through them.

has a scope).

order without some manual editing. On the other hand, now we may have a circular dependency between modules.

but we don't want to prune the global variables away.

without introducing circular dependency, 2) Don't try to create initializers for types that are not at the module level.

ecrad).

pratyai marked this pull request as ready for review February 24, 2025 22:07

pratyai requested a review from acalotoiu February 24, 2025 22:09

pratyai force-pushed the glob branch from 9828a2a to 9c04dbf Compare February 25, 2025 13:19

pratyai added 12 commits February 25, 2025 17:56

Write statements do not modify the arguments (notably, not the stream

4f9b678

handler integer itself), so we can const propagate through them.

replace equality with identity

e504954

Components do not exactly have scopes (we need to go to the root, which

9b17a8b

has a scope).

Generate init fn always.

9583677

Global data consolidation

e2cfa5a

Adjust for the drastic change of fparser processing for create ast test.

b86ac8d

Don't always add an empty global data to args.

74b66bd

Handle the part-refs when replacing with global data-refs.

97d9eba

Don't move the derived types around, because then the serde goes out of

f33bd01

order without some manual editing. On the other hand, now we may have a circular dependency between modules.

We also want to have the global data structure before generating serde;

0b6ff49

but we don't want to prune the global variables away.

Avoid duplicate name.

9931174

1) TODO the fact that we cannot handle global objects of derived type

202d56e

without introducing circular dependency, 2) Don't try to create initializers for types that are not at the module level.

pratyai force-pushed the glob branch from f83eb92 to 202d56e Compare February 25, 2025 16:56

pratyai added 3 commits February 25, 2025 18:23

Global data is a special case for serde (because it ties to the real

2c9b10a

ecrad).

Fix the not expression.

a949a3f

Print operator.

1ed8a72

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[f2dace/dev, fortran] 1) Consolidate global data objects into a single struct, 2) Then pass it around in the processed AST as function arguments, 3) Try to keep the global data serialisation and deserialisation in sync. #1951

[f2dace/dev, fortran] 1) Consolidate global data objects into a single struct, 2) Then pass it around in the processed AST as function arguments, 3) Try to keep the global data serialisation and deserialisation in sync. #1951

pratyai commented Feb 24, 2025

pratyai commented Feb 24, 2025

[f2dace/dev, fortran] 1) Consolidate global data objects into a single struct, 2) Then pass it around in the processed AST as function arguments, 3) **Try** to keep the global data serialisation and deserialisation in sync. #1951

Are you sure you want to change the base?

[f2dace/dev, fortran] 1) Consolidate global data objects into a single struct, 2) Then pass it around in the processed AST as function arguments, 3) **Try** to keep the global data serialisation and deserialisation in sync. #1951

Conversation

pratyai commented Feb 24, 2025

pratyai commented Feb 24, 2025

[f2dace/dev, fortran] 1) Consolidate global data objects into a single struct, 2) Then pass it around in the processed AST as function arguments, 3) Try to keep the global data serialisation and deserialisation in sync. #1951

[f2dace/dev, fortran] 1) Consolidate global data objects into a single struct, 2) Then pass it around in the processed AST as function arguments, 3) Try to keep the global data serialisation and deserialisation in sync. #1951