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

Moved complex overloads for mac to inline from cpp. #664

Merged
merged 2 commits into from
Mar 29, 2019

Conversation

economon
Copy link
Member

Proposed Changes

Give a brief overview of your contribution here in a few sentences.

The latest llvm version on mac throws a compile error due to not being able to find some overloaded functions for complex numbers. Moving the overloads from the cpp file to the inline file appears to fix the linkage issue.

Related Work

Resolve any issues (bug fix or feature request), note any related PRs, or mention interactions with the work of others, if any.

N/A

PR Checklist

Put an X by all that apply. You can fill this out after submitting the PR. If you have any questions, don't hesitate to ask! We want to help. These are a guide for you to know what the reviewers will be looking for in your contribution.

  • I am submitting my contribution to the develop branch.
  • My contribution generates no new compiler warnings (try with the '-Wall -Wextra -Wno-unused-parameter -Wno-empty-body' compiler flags).
  • My contribution is commented and consistent with SU2 style.

Copy link

@Sehlingdorf Sehlingdorf left a comment

Choose a reason for hiding this comment

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

Edit: Wrong account used, see review below. I can't delete the comment so I just edited it.

Copy link
Contributor

@TobiKattmann TobiKattmann left a comment

Choose a reason for hiding this comment

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

Hi,
as it is 30 lines of copied code which only affects Apple Os's and fixes your compile error... LGTM.
Although the ad_structure.cpp should contain the same code after all preprocessor statements (#include etc) are executed, right? Did you look at that by any chance with the -E (for gnu, maybe different for LLVM) compiler flag. If not, then I guess it is better to not waist time on that.
Best regards, Tobi

(Sorry used another account before without noticing)

@talbring
Copy link
Member

Seems like a quick fix. LGTM

@talbring talbring merged commit 34cf674 into develop Mar 29, 2019
@economon economon deleted the fix_complex_mac branch April 1, 2019 17:28
Sign up for free to 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.

4 participants