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

Allow import scripts to parse huge .net files #1483

Merged
merged 1 commit into from
Jun 23, 2020

Conversation

rw1nkler
Copy link
Contributor

@rw1nkler rw1nkler commented May 12, 2020

This commit changes the architecture importing scripts and allows them to parse huge .net files. Without these changes, libxml fails on using XPath expressions due to the internal memory allocation limit. In that situation, the python wrapper on the libxml library throws misleading error message about incorrect XPath expression.

This changes are required for OpenTitan and are related to #1442 (comment)

@litghost
Copy link
Contributor

The description of the commit and the PR is rather poor. Please re-write it. These changes are required for OpenTitan, but have nothing to do with OpenTitan per say.

@rw1nkler rw1nkler mentioned this pull request May 12, 2020
@rw1nkler rw1nkler changed the title Change importing scripts for OpenTitan Importing scripts fixes required for generating OpenTitan design May 12, 2020
@probot-autolabeler probot-autolabeler bot added lang-python Issue uses (or requires) Python language. type-utils Issues is related to the scripts inside the repo. labels May 13, 2020
@rw1nkler rw1nkler changed the title Importing scripts fixes required for generating OpenTitan design Allow importing scripts to parse huge .net files May 13, 2020
@rw1nkler rw1nkler changed the title Allow importing scripts to parse huge .net files Allow import scripts to parse huge .net files May 13, 2020
@rw1nkler rw1nkler requested a review from mkurc-ant June 9, 2020 16:28
This commit changes the architecture importing scripts and allows them
to parse huge .net files. Without these changes, libxml fails on using
XPath expressions due to the internal memory allocation limit.
In that situation, the python wrapper on the libxml library throws
misleading error message about incorrect XPath expression.

Signed-off-by: Robert Winkler <rwinkler@antmicro.com>
Copy link
Collaborator

@mkurc-ant mkurc-ant left a comment

Choose a reason for hiding this comment

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

LGTM

@rw1nkler rw1nkler requested a review from litghost June 23, 2020 12:19
Copy link
Contributor

@litghost litghost left a comment

Choose a reason for hiding this comment

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

If this works, great! I surprised this worked.

@litghost litghost requested a review from HackerFoo June 23, 2020 16:37
@litghost
Copy link
Contributor

@HackerFoo Any additional thoughts?

Copy link
Contributor

@HackerFoo HackerFoo left a comment

Choose a reason for hiding this comment

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

Only slightly more verbose, so this seems like a great solution if it reduces overhead.

@litghost litghost merged commit 0a2ff13 into f4pga:master Jun 23, 2020
@umarcor umarcor deleted the fix_xpath branch March 22, 2022 21:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lang-python Issue uses (or requires) Python language. type-utils Issues is related to the scripts inside the repo.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants