Skip to content
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

Get beyond one type of Intel bugs #120

Merged
merged 2 commits into from
Feb 8, 2024
Merged

Conversation

ktras
Copy link
Collaborator

@ktras ktras commented Feb 6, 2024

@rouson The ifx bugs we are facing in inference-engine are a result of the use-stmts for the dependency sourcery. This branch shows that if all of the use sourcery_m statements are replaced with use-stmts referencing the actual module where the named object lives, then ifx doesn't complain. It does eventually hit another compiler error (probably related to issues with many nested associate-stmts). I have tried to write a reproducer (unsuccessfully because the reproducers I have written successfully compile with ifx) but I will continue to try and maybe at some point we could look together at how to create a reproducer for this wrapper module issue. (This branch is branched off of the branch bugfixes-for-nag)

@ktras ktras changed the title DRAFT - Not to be merged - Attempt to expose intel bug DRAFT - Not to be merged - Attempt to expose ifx bug Feb 6, 2024
@rouson
Copy link
Contributor

rouson commented Feb 6, 2024

@ktras nice work! Yes, let's look at this together.

@ktras ktras changed the title DRAFT - Not to be merged - Attempt to expose ifx bug Get beyond one type of Intel bugs Feb 8, 2024
@ktras ktras marked this pull request as ready for review February 8, 2024 22:53
Copy link
Contributor

@rouson rouson left a comment

Choose a reason for hiding this comment

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

LGTM

@rouson rouson merged commit 1132940 into main Feb 8, 2024
4 checks passed
@rouson rouson deleted the attempt-to-expose-intel-bug branch February 8, 2024 22:53
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