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

added const SOCK_SEQPACKET, and SOCK_RDM where applicable #300

Merged
merged 1 commit into from
May 27, 2016

Conversation

rrichardson
Copy link
Contributor

... which is used for UNIX Seqpacket sockets as well as SCTP IP.

I have verified in source on a couple Linux flavours as well as freebsd and darwin source that SOCK_SEQPACKET has value 5.
Solaris is the odd one with a value of 6. I also added RDM for solaris (value 5)

@rust-highfive
Copy link

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

@alexcrichton
Copy link
Member

@bors: r+ df0a9ba

bors added a commit that referenced this pull request May 27, 2016
added const SOCK_SEQPACKET,  and SOCK_RDM where applicable

... which is used for UNIX Seqpacket sockets as well as SCTP IP.

I have verified in source on  a couple Linux flavours as well as freebsd and darwin source that SOCK_SEQPACKET has value 5.
Solaris is the odd one with a value of 6.  I also added RDM for solaris (value 5)
@bors
Copy link
Contributor

bors commented May 27, 2016

⌛ Testing commit df0a9ba with merge 4bcee37...

@bors
Copy link
Contributor

bors commented May 27, 2016

💔 Test failed - travis

@rrichardson
Copy link
Contributor Author

Looks like networking failed in the openbsd test.

@semarie
Copy link
Contributor

semarie commented May 27, 2016

it is due to maintenance on ftp5 : https://marc.info/?l=openbsd-misc&m=146427439004957

@alexcrichton
Copy link
Member

@bors: retry

@bors
Copy link
Contributor

bors commented May 27, 2016

⌛ Testing commit df0a9ba with merge 6021251...

bors added a commit that referenced this pull request May 27, 2016
added const SOCK_SEQPACKET,  and SOCK_RDM where applicable

... which is used for UNIX Seqpacket sockets as well as SCTP IP.

I have verified in source on  a couple Linux flavours as well as freebsd and darwin source that SOCK_SEQPACKET has value 5.
Solaris is the odd one with a value of 6.  I also added RDM for solaris (value 5)
@bors
Copy link
Contributor

bors commented May 27, 2016

💔 Test failed - status-appveyor

@alexcrichton
Copy link
Member

@bors: retry

On Fri, May 27, 2016 at 11:18 AM, bors notifications@github.com wrote:

💔 Test failed - status-appveyor
https://ci.appveyor.com/project/alexcrichton/libc/build/1.0.1267


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#300 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AAD95EutgjfSRZX3iY1WGkANtJJvQTuqks5qFzV2gaJpZM4IoJzV
.

bors added a commit that referenced this pull request May 27, 2016
added const SOCK_SEQPACKET,  and SOCK_RDM where applicable

... which is used for UNIX Seqpacket sockets as well as SCTP IP.

I have verified in source on  a couple Linux flavours as well as freebsd and darwin source that SOCK_SEQPACKET has value 5.
Solaris is the odd one with a value of 6.  I also added RDM for solaris (value 5)
@bors
Copy link
Contributor

bors commented May 27, 2016

⌛ Testing commit df0a9ba with merge 85af2c8...

@bors
Copy link
Contributor

bors commented May 27, 2016

💔 Test failed - travis

@alexcrichton
Copy link
Member

@bors: retry

On Fri, May 27, 2016 at 11:53 AM, bors notifications@github.com wrote:

💔 Test failed - travis
https://travis-ci.org/rust-lang/libc/builds/133449897


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#300 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AAD95D5k8Lcx6_qJHJXjsEQ7oehumXW2ks5qFz2NgaJpZM4IoJzV
.

@bors
Copy link
Contributor

bors commented May 27, 2016

⌛ Testing commit df0a9ba with merge bb4dabb...

bors added a commit that referenced this pull request May 27, 2016
added const SOCK_SEQPACKET,  and SOCK_RDM where applicable

... which is used for UNIX Seqpacket sockets as well as SCTP IP.

I have verified in source on  a couple Linux flavours as well as freebsd and darwin source that SOCK_SEQPACKET has value 5.
Solaris is the odd one with a value of 6.  I also added RDM for solaris (value 5)
@bors
Copy link
Contributor

bors commented May 27, 2016

☀️ Test successful - status-appveyor, travis

@bors bors merged commit df0a9ba into rust-lang:master May 27, 2016
Susurrus pushed a commit to Susurrus/libc that referenced this pull request Mar 26, 2017
Susurrus pushed a commit to Susurrus/libc that referenced this pull request Mar 26, 2017
danielverkamp pushed a commit to danielverkamp/libc that referenced this pull request Apr 28, 2020
This was historically done as the contents of the `i686` module wouldn't
actually compile on i586 for various reasons. I believe I've tracked this down
to rust-lang#300 where LLVM refuses to compile a function using the `x86_mmx` type
without actually enabling the `mmx` feature (sort of reasonably so!). This
commit will now compile in both the `i586` and `i686` modules of this crate into
the `i586-unknown-linux-gnu` target, and the relevant functions now also enable
the `mmx` feature if they're using the `__m64` type.

I believe this is uncovering a more widespread problem where the `__m64` isn't
usable outside the context of `mmx`-enabled functions. The i686 and x86_64
targets have this feature enabled by default which is why it's worked there, but
they're not enabled for the i586 target. We'll probably want to consider this
when stabilizing!
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.

None yet

5 participants