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

pythonPackages.tensorflow: add flags for efficent math on CPU #30786

Merged
merged 1 commit into from Nov 4, 2017

Conversation

jyp
Copy link
Contributor

@jyp jyp commented Oct 25, 2017

Motivation for this change

Make tensorflow more efficient on CPU

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

@@ -7,6 +7,9 @@
, cudaSupport ? false, nvidia_x11 ? null, cudatoolkit ? null, cudnn ? null
# Default from ./configure script
, cudaCapabilities ? [ "3.5" "5.2" ]
, sse42Support ? false
, avx2Support ? false
, fmaSupport ? false
Copy link
Member

Choose a reason for hiding this comment

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

What happens if this is enabled, but not supported by the hardware? Would it still works?

@jyp
Copy link
Contributor Author

jyp commented Oct 26, 2017 via email

@abbradar
Copy link
Member

abbradar commented Nov 4, 2017

@Mic92 No, it wouldn't -- TensorFlow doesn't support dynamic code paths depending on runtime architecture.

Thanks!

@abbradar abbradar merged commit 6269306 into NixOS:master Nov 4, 2017
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.

None yet

4 participants