-
Notifications
You must be signed in to change notification settings - Fork 8
fix: Add back support for ppc64le #35
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
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -17,7 +17,7 @@ namespace std { | |
| seed ^= hasher(v) + 0x9e3779b9 + (seed << 6) + (seed >> 2); | ||
| } | ||
|
|
||
| #if defined(__x86_64__) || defined(__i386__) | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I would limit it here just to and for the sake of consistency, see https://sourceforge.net/p/predef/wiki/Architectures/ There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @andriish Can you elaborate on what you mean by "consistency"? I'm not sure what you're trying to communicate and the link isn't informative. I'm sure to you it is clear, but I'm going to need you to write out your point. |
||
| #if defined(__x86_64__) || defined(__i386__) || defined(__PPC64__) || defined(__ppc64__) || defined(_ARCH_PPC64) | ||
| template <> | ||
| struct hash<ql::qdouble> : public __hash_base<size_t, ql::qdouble> | ||
| { | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, Something like
would be better.
But it is important to list supported architectures explicitly, and not "everything but...".
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@andriish Can you explain more on why? How is this different or better? Is there another architecture that supports
float128that you know of? Or do you mean that there could be other architectures not considered here that also don't supportlibquadmathand these would get picked up erroneously here?