Skip to content

Fix DragonFly: clock_gettime() expects CLOCK_* constants as ulong. #222

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

Merged
merged 1 commit into from
Mar 11, 2016
Merged

Fix DragonFly: clock_gettime() expects CLOCK_* constants as ulong. #222

merged 1 commit into from
Mar 11, 2016

Conversation

mneumann
Copy link
Contributor

While there add all CLOCK_ constants as found on DragonFly.

While there add all CLOCK_ constants as found on DragonFly.
@alexcrichton
Copy link
Member

@bors: r+ 378bb73

Let's see if this works...

@bors
Copy link
Contributor

bors commented Mar 11, 2016

⌛ Testing commit 378bb73 with merge ef979ef...

bors added a commit that referenced this pull request Mar 11, 2016
Fix DragonFly: clock_gettime() expects CLOCK_* constants as ulong.

While there add all CLOCK_ constants as found on DragonFly.
@bors
Copy link
Contributor

bors commented Mar 11, 2016

☀️ Test successful - status-appveyor, travis

@bors bors merged commit 378bb73 into rust-lang:master Mar 11, 2016
@mneumann mneumann deleted the dragonfly_clock_gettime branch March 11, 2016 23:18
@mneumann mneumann restored the dragonfly_clock_gettime branch December 4, 2016 12:23
danielverkamp pushed a commit to danielverkamp/libc that referenced this pull request Apr 28, 2020
…#223)

* Adds extract_unchecked + replace_unchecked + len (rust-lang#222 )

* [x86] Fixes the return types + uses extract_unchecked for:
  * _mm_extract_epi8
  * _mm_extract_epi16
  * _mm256_extract_epi8
  * _mm256_extract_epi16

* Minor changes to the other extract_epi* intrinsics for style consistency
These should now zero-extend the extracted int and behave appropriately. An old typo makes these a bit confusing, See this llvm issue.
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.

3 participants