summaryrefslogtreecommitdiff
path: root/scripts/gcc-wrapper.py (follow)
Commit message (Collapse)AuthorAge
* scripts: Clean up the gcc-wrapper white listPrasad Sodagudi2020-06-23
| | | | | | | | | | Update the white list of warnings for the latest kernel release based on current CFLAG settings. Disabled undefined-optimized and tautological features, so clean up the gcc-wrapper list based on current settings. Change-Id: If6a733c35b4b09b2357ced7997fb2ff16204c766 Signed-off-by: Prasad Sodagudi <psodagud@codeaurora.org>
* scripts: set clang as REAL_CC to support LLVM by defaultSatya Durga Srinivasu Prabhala2020-06-23
| | | | | | | | | | | | To support LLVM by default, set REAL_CC to clang which overrides gcc. Also, white list warnings which are being treated as errors while compiling Kernel with clang compiler. Change-Id: I5df2375cb8a2f424521fdd862d550ab340a34c98 Signed-off-by: Satya Durga Srinivasu Prabhala <satyap@codeaurora.org> Signed-off-by: Naitik Bharadiya <bharad@codeaurora.org>
* scripts: gcc-wrapper: Route the GCC errors to stderrShadab Naseem2019-03-29
| | | | | | | | | | | | The GCC wrapper writes any error message from GCC to stdout along with the messages from the wrapper itself. This is okay for most case, but when GCC is used with -print-xxx flags, the stdout output is supposed to be taken as input to some other build command, so putting error messages in there is pretty bad. Fix this by writing error messages to stderr. Change-Id: I4656033f11ba5212fdcc884cc588f8b9d2c23419 Signed-off-by: Shadab Naseem <snaseem@codeaurora.org>
* scripts: gcc-wrapper: allow a few forbidden warningsDavid Keitel2016-03-23
| | | | | | Bypass a few forbidden warnings to allow msm_defconfig to build. Signed-off-by: David Keitel <dkeitel@codeaurora.org>
* scripts: Call out python2 explicitlyDavid Brown2016-03-23
| | | | | | | | | | | | | Many systems these days have both python2 and python3 installed. The unversioned executable `python` may point to either version. Per https://www.python.org/dev/peps/pep-0394/ , scripts that need Python 2 should explicitly call this out in the shebang line. These build scripts are both specific to python 2, so call this out in the shebang line. Change-Id: I11f70c341e484254dc1679db65c2ed5ac61e510f Signed-off-by: David Brown <davidb@codeaurora.org>
* scripts: gcc-wrapper: bypass forbidden warnings with gcc5Se Wang (Patrick) Oh2016-03-23
| | | | | | | | | | | Bypass forbidden warnings in code coming from upstream in order to avoid compilation errors with gcc5. sysrq.c:956:33: warning: array subscript is above array bounds hci_sock.c:980:8: warning: passing argument 2 of 'hci_test_bit' discards 'const' qualifier from pointer target type Change-Id: I5056078112fdc457c424c0f49c4dca70c6b97c29 Signed-off-by: Se Wang (Patrick) Oh <sewango@codeaurora.org>
* scripts: gcc-wrapper: Allow upstream forbidden warningsIan Maund2016-03-23
| | | | | | | | Bypass forbidden warnings in code coming from upstream in order to avoid compilation errors for msm-3.18 and remove bypassed warnings from msm-3.14. Signed-off-by: Ian Maund <imaund@codeaurora.org>
* scripts: gcc-wrapper: Use wrapper to check compiler warningsDavid Brown2016-03-23
Rather than telling gcc to make warnings as errors, and then hunting down make rules to disable this, leave them as warnings, but invoke gcc through a wrapper that checks the warnings against a whitelist. The initial whitelist comes from the warnings in the current build, all of which have been allowed through Make overrides. Change-Id: I5e0b199f9803d072537eeb77cb38d91cc06e951b Signed-off-by: David Brown <davidb@codeaurora.org> [mattw@codeaurora.org: update allowed_warnings for msm-3.14] Signed-off-by: Matt Wagantall <mattw@codeaurora.org>