Skip to content

Conversation

@gmaxwell
Copy link
Contributor

The constraint "n" is a more obscure setting which is needed for
special cases that don't apply to our use.

Use of "n" exposed some bugs in pre-release versions of clang.
This fixes #594

The constraint "n" is a more obscure setting which is needed for
 special cases that don't apply to our use.

Use of "n" exposed some bugs in pre-release versions of clang.
This fixes #594
@gmaxwell
Copy link
Contributor Author

I know the issue has been closed, but since this was reported multiple times independently (in bitcoin repo too) we're likely to see more of it.

@sipa
Copy link
Contributor

sipa commented Mar 10, 2019

utACK d58bc93

@real-or-random
Copy link
Contributor

utACK d58bc93

@gmaxwell gmaxwell merged commit d58bc93 into bitcoin-core:master Mar 11, 2019
gmaxwell added a commit that referenced this pull request Mar 11, 2019
… values.

d58bc93 Switch x86_64 asm to use "i" instead of "n" for immediate values. (Gregory Maxwell)

Pull request description:

  The constraint "n" is a more obscure setting which is needed for
   special cases that don't apply to our use.

  Use of "n" exposed some bugs in pre-release versions of clang.
  This fixes #594

Tree-SHA512: 1ffba02aa6bfcd0b6f731196e5d007f4ddb0f03f53b30a2633f0e376578cf7f828570579502f2de721dcda8034fd8e7bea822542bf36032d98ef802b4cf27725
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Build issue with clang8 on amd64

3 participants