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

New module names break file-specific flags #11202

Closed
mratsim opened this issue May 8, 2019 · 1 comment

Comments

Projects
None yet
3 participants
@mratsim
Copy link
Collaborator

commented May 8, 2019

For SIMD vectorization I need to pass file-specific compilation flags so that I can handle multiple architecture with the same binary.

However with the new changes I can't compile anymore because the naming changed.
What are the new rules for the names?

image

This is related to #11196 and 0121dda

By the way, the ability to pass per-file compilation flag would be very useful because everyone would have to copy my nim.cfg otherwise.

@mratsim mratsim added the Tools label May 8, 2019

@Araq Araq added Regression and removed Tools labels May 9, 2019

@alaviss

This comment has been minimized.

Copy link
Contributor

commented May 14, 2019

By the way, the ability to pass per-file compilation flag would be very useful because everyone would have to copy my nim.cfg otherwise.

Does the {.passC.} pragma not work?

@Araq Araq closed this in 651ae68 May 14, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.