Skip to content

ARROW-10489: [C++] Add Intel C++ compiler options for different warning levels - #9266

Closed
jcmuel wants to merge 2 commits into
apache:masterfrom
jcmuel:master
Closed

ARROW-10489: [C++] Add Intel C++ compiler options for different warning levels#9266
jcmuel wants to merge 2 commits into
apache:masterfrom
jcmuel:master

Conversation

@jcmuel

Copy link
Copy Markdown
Contributor

@pitrou

Copy link
Copy Markdown
Member

Thank you for the PR @jcmuel ! Can you also make sure the two other BUILD_WARNING_LEVEL codepaths build fine?

…EVEL == EVERYTHING and Production. In both cases, we simply use -Wall.

@pitroupitrou left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thank you @jcmuel . Will merge if CI is green.

@jcmuel

Copy link
Copy Markdown
ContributorAuthor

I just added the missing code path, and adjusted the production code path, such that it uses "/Wall" on Intel for Windows. Not sure if this is necessary, but I did it for the sake of consistency with the other two code paths.

@pitroupitrou changed the title ARROW-10489: [C++] Add Intel C++ compiler options for BUILD_WARNING_LEVEL == CHECKINARROW-10489: [C++] Add Intel C++ compiler options for different warning levelsJan 19, 2021
@pitrou

Copy link
Copy Markdown
Member

Those warnings are mainly for development, but useful anyway.

@github-actions

Copy link
Copy Markdown

kszucs pushed a commit that referenced this pull request Jan 25, 2021
…ng levels
See [Intel Compiler warning flag documentation](https://software.intel.com/content/www/us/en/develop/documentation/cpp-compiler-developer-guide-and-reference/top/compiler-reference/error-handling-1/warnings-errors-and-remarks.html).
Closes#9266 from jcmuel/master
Authored-by: Johannes Müller <JohannesMueller@fico.com>
Signed-off-by: Antoine Pitrou <antoine@python.org>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@jcmuel@pitrou