summaryrefslogtreecommitdiff
path: root/numpy/distutils/fcompiler/intel.py
Commit message (Collapse)AuthorAgeFilesLines
* BUG: Flags should not contain spacesEric Wieser2020-01-231-4/+4
| | | | | | It's very unlikely that `ifort` is supposed to be invoked as `ifort "-fpmodel strict"` instead of `ifort -fpmodel strict` . Spaces in flag items will end up passed as a single argument.
* MAINT: Remove unnecessary 'from __future__ import ...' statementsJon Dufresne2020-01-031-2/+0
| | | | | As numpy is Python 3 only, these import statements are now unnecessary and don't alter runtime behavior.
* BUG: Do not double-quote arguments passed on to the linkerEric Wieser2019-01-301-1/+4
| | | | | | | | | | | | | After the recent patch to CCompiler.spawn, the file-paths no longer need manual quoting - that's handled as needed within subprocess. This also states our assumption that our paths do not contain commas. If we care about this, we could adopt the approach used by https://github.com/rust-lang/rust/issues/38795. Tested for gcc locally by looking at the error messages of `subprocess.check_call(["gcc", r'-Wl,spaces and no quotes'])` Other fortran compiler changes not tested, but assumed to be broken in the same way. Fixes #12882
* MAINT: distutils: trivial cleanupsxoviat2017-11-061-4/+2
|
* BLD: remove -xhost flag from IntelFCompiler. Closes gh-9042.Ralf Gommers2017-07-271-1/+1
| | | | | Note that this was discussed extensively in gh-7287, but removing this -xhost flag was missed in the PR that closed that issue.
* BUG: Fix Intel compilation on Unix.Charles Harris2017-06-261-2/+2
| | | | | | | | | | | Fixes two problems: * c compilers do not have a find_executables method. * get_version return a LooseVersion instance, not string. Closes #9278. [ci skip]
* MAINT: Update Intel compiler options.Charles Harris2017-04-191-2/+6
| | | | | | | | | The '-openmp' option was deprecated in Intel version 15 and removed in version 18. The replacement is '-qopenmp'. Closes #8941. [skip ci]
* DEP: Fix escaped string characters deprecated in Python 3.6.Charles Harris2016-12-141-1/+1
| | | | | | | In Python 3.6 a number of escape sequences that were previously accepted -- for instance "\(" that was translated to "\\(" -- are deprecated. To retain the previous behavior either raw strings must be used or the backslash must be properly escaped itself.
* BLD: Remove Intel compiler flag -xSSE4.2Charles Harris2016-05-221-2/+2
| | | | | | | The consensus seems to be that hardcoding SSE4.2 results in poor code for architectures lacking the feature. Closes #7287.
* DOC: Comment all O1s [ci skip]Eric Larson2015-12-281-2/+2
|
* FIX: Fix MKL for LinuxEric Larson2015-12-281-2/+2
|
* BLD: do not build exclusively for SSE4.2 processorsChristoph Gohlke2015-10-091-1/+1
|
* MSVCCompiler overwrite 'lib' and 'include' environment variables. ThisDmitry Zagorny2015-09-151-15/+14
| | | | | | | | | behavior affect at least python 3.5 and SciPy build and build failed. During initialization <python>.distutils.MSVCCompiler replace Intel environment('include' and 'lib' paths). This fix decorate 'initialize' function in MSVCCompiler and extend 'lib' and 'include' environment variables. Changed compilation keys: generate optimized code specialized for Intel processors with SSE4.2 support.
* BUG: fix 32-bit arch flag for Intel Fortran compiler.Ralf Gommers2015-08-201-1/+1
| | | | See https://software.intel.com/en-us/node/524904. Reported in gh-6095.
* BUG: rpath was not implemented for numpy.distutils.fcompilerNick Papior Andersen2015-02-271-0/+13
| | | | | | | | | | | | | | | | This bug-fix only applies for non gnu-compilers. The fortran compilers in numpy inherited the Ccompier class which had the runtime library directories NotImplemented. Hence the compilers need to define their own runtime library path. I have added that information to the intel/pgi/sun compilers. The rest are either already implemented or I do not know them. I have tested the bug-fix with intel compilers of numpy AND the subsequent installation of scipy (which relies on the fortran compilers). Hence this bug will only occur when linking with the fortran compilers.
* DEV: Replace deprecated options for ifort.Åsmund Hjulstad2015-02-101-1/+1
| | | | | The /Qlowercase and /us options has been deprecated in the Intel Visual Fortran Compiler since at least version 2013. Replace with /names:lowercase and /assume:underscore.
* BLD: remove "-Wl,-framework,Python" from linker flags for Intel compiler.Ralf Gommers2014-04-211-1/+1
| | | | | | | | | The "-Wl,-undefined,dynamic_lookup" flag is enough to make things work with OS X bundles. On the mailing list an issue was reported with Anaconda (non-framework build) where f2py was picking up the system framework Python instead of the Anaconda one. Thanks to Robert Kern for explaining how to fix this.
* BUG: ifort has issues with optimization flag /O2cgohlke2014-04-081-1/+1
| | | Fixes scipy test failures.
* STY: Giant comma spacing fixup.Charles Harris2013-08-181-7/+7
| | | | | | | Run the 2to3 ws_comma fixer on *.py files. Some lines are now too long and will need to be broken at some point. OTOH, some lines were already too long and need to be broken at some point. Now seems as good a time as any to do this with open PRs at a minimum.
* ENH: remove obsolete ifort flags, ensure generated binaries work everywhere.David Cournapeau2013-04-231-14/+5
|
* 2to3: Apply `print` fixer.Charles Harris2013-04-061-1/+1
| | | | | | | Add `print_function` to all `from __future__ import ...` statements and use the python3 print function syntax everywhere. Closes #3078.
* 2to3: Use absolute imports.Charles Harris2013-03-281-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The new import `absolute_import` is added the `from __future__ import` statement and The 2to3 `import` fixer is run to make the imports compatible. There are several things that need to be dealt with to make this work. 1) Files meant to be run as scripts run in a different environment than files imported as part of a package, and so changes to those files need to be skipped. The affected script files are: * all setup.py files * numpy/core/code_generators/generate_umath.py * numpy/core/code_generators/generate_numpy_api.py * numpy/core/code_generators/generate_ufunc_api.py 2) Some imported modules are not available as they are created during the build process and consequently 2to3 is unable to handle them correctly. Files that import those modules need a bit of extra work. The affected files are: * core/__init__.py, * core/numeric.py, * core/_internal.py, * core/arrayprint.py, * core/fromnumeric.py, * numpy/__init__.py, * lib/npyio.py, * lib/function_base.py, * fft/fftpack.py, * random/__init__.py Closes #3172
* 2to3: Put `from __future__ import division in every python file.Charles Harris2013-03-011-0/+1
| | | | | | | | This should be harmless, as we already are division clean. However, placement of this import takes some care. In the future a script can be used to append new features without worry, at least until such time as it exceeds a single line. Having that ability will make it easier to deal with absolute imports and printing updates.
* MAINT: update Intel Fortran compiler flags for the 21st century.Ralf Gommers2012-09-091-55/+16
| | | | | | Thanks to Intel for this contribution. Note that there's also an MKL application note which recommends these flags: http://software.intel.com/en-us/articles/numpyscipy-with-intel-mkl
* BUG: '-framework Python' is not needed and can interfere.Robert Kern2012-05-311-1/+1
|
* BUG: numpy doesn't compile anymore with ifort using -O3, changing to -O1.Ralf Gommers2011-04-221-2/+2
| | | | Closes #1378. Thanks to Burkhard Neinhues and Christoph Gohlke.
* BUG: fix 64-bit Intel Fortran compiler detection. Closes #1448.rgommers2011-03-091-4/+4
|
* Apply ifort.patch from ticket #1372 to allow Intel Fortran Compiler 11.1 to ↵Travis Oliphant2010-01-241-3/+15
| | | | be called by numpy.distutils.
* 3K: distutils: remove unnecessary non-ascii characters in intel.pyPauli Virtanen2009-12-061-8/+0
|
* Fix print statements in fcompiler for python3.David Cournapeau2009-12-031-1/+1
|
* BUG: update version_match for recent version of ifort for IA-64 (#1145).David Cournapeau2009-06-201-1/+1
|
* Also link with Python.Robert Kern2007-12-161-1/+1
|
* Typo.Robert Kern2007-12-041-1/+1
|
* Use the correct link parameters for shared libraries with Intel Fortran on OS X.Robert Kern2007-12-041-0/+10
|
* The PIC flag changed in the 10 version of the Intel Fortran compiler.Robert Kern2007-12-041-10/+8
|
* * Allow an Intel Fortran 10.0 for 64-bit version string that I've seen in ↵Robert Kern2007-08-031-1/+9
| | | | | | the wild. * Use -fPIC instead of -KPIC for said wild compiler.
* Add support for aliases for Fortran compilers.cookedm2007-07-061-0/+3
| | | | - 'g77' for gnu, 'gfortran' for gnu95, 'ifort' for intel
* Better version handling in fcompilercookedm2007-06-151-23/+21
| | | | | | | | | | | | | | | | | | | | | | * Remove FCompiler.get_version_cmd, FCompiler.get_flags_version, FCompiler.get_linker_so_cmd, and FCompiler.get_linker_exe_cmd; subclasses should do this in FCompiler.update_executables() * FCompiler attributes .compiler_f77, .version_cmd, etc., are now properties that read from the .executables dictionary. * Update intel.py and absoft.py for above * Add extra asserts for defensive programming. Most of our problems here seem to come from bad values being generated, and the error not being caught until later. * must call FCompiler.customize() before FCompiler.get_version(); command/build_ext.py and command/config.py updated * verify that commands make sense earlier -- must be None or lists of strings Also, * add IA-32 as another pattern to search for in 32-bit Intel compiler version. * minor formatting * add debugging helpers to environment.py:EnvironmentConfig class
* Updated intel compiler arch flags -- intel compiler users should recheck ↵Pearu Peterson2007-06-051-2/+20
| | | | these options.
* fix my mistake in fcompiler/absoft.py and fcompiler/intel.pycookedm2007-05-281-9/+9
|
* Better temporary file handling by using one temporary directory forcookedm2007-05-281-10/+13
| | | | numpy.distutils, and removing that at exit. Replaces using tempfile.mktemp.
* distutils: clean up imports (found by running pyflakes)cookedm2007-05-251-3/+0
|
* merge from distutils-revamp branch (step 2)cookedm2007-05-251-39/+40
| | | | | | - fcompiler changes. All flags, executables, etc., should be overridable by the user with config_fc (either command line or setup.cfg) or by environment variables
* #520: don't add arch-specific flags when linking with Intel Fortrancookedm2007-05-151-1/+0
|
* Better version handling for gnu and intel Fortran compilerscookedm2007-04-221-12/+17
| | | | | | | | | - gnu compilers check if the version is >= 4, in which case it's gfortran - add a test file for gnu compiler check - simplify version matching on intel compilers to be more flexible - add FCompiler.find_executables so that subclasses can find executables at .customize() time, instead of when the class is created.
* Fix missing comment characters in intel.py. Check for None in .reshape and ↵Travis Oliphant2006-10-191-4/+4
| | | | .resize
* Add Intel Itanium compiler 9.x support (needs testing).Pearu Peterson2006-10-191-6/+11
|
* fix #234: IntelVisualFCompiler is brokencookedm2006-08-081-3/+0
|
* fix arch flags for ifort on machines in em64t modecookedm2006-07-171-0/+6
|
* Add Intel EM64T Fortran Compiler support.Pearu Peterson2006-04-091-2/+23
|
View Lorry Controller Status