Skip to content

Commit 1d8b116

Browse files
nnethercotennethercote
committed
Add libc-0.2.124 
1 parent 272e7d6 commit 1d8b116

File tree

217 files changed

+94135
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

217 files changed

+94135
-0
lines changed

‎collector/benchmarks/libc-0.2.124/.cargo_vcs_info.json

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
{
2+
"git": {
3+
"sha1": "02f4f6cbccaf2c7cc22617a51f9717d5ac6c9a05"
4+
},
5+
"path_in_vcs": ""
6+
}

‎collector/benchmarks/libc-0.2.124/.gitignore

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
target
2+
Cargo.lock
3+
*~
4+
style

‎collector/benchmarks/libc-0.2.124/CONTRIBUTING.md

Lines changed: 89 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,89 @@
1+
# Contributing to `libc`
2+
3+
Welcome! If you are reading this document, it means you are interested in contributing
4+
to the `libc` crate.
5+
6+
## Adding an API
7+
8+
Want to use an API which currently isn't bound in `libc`? It's quite easy to add
9+
one!
10+
11+
The internal structure of this crate is designed to minimize the number of
12+
`#[cfg]` attributes in order to easily be able to add new items which apply
13+
to all platforms in the future. As a result, the crate is organized
14+
hierarchically based on platform. Each module has a number of `#[cfg]`'d
15+
children, but only one is ever actually compiled. Each module then reexports all
16+
the contents of its children.
17+
18+
This means that for each platform that libc supports, the path from a
19+
leaf module to the root will contain all bindings for the platform in question.
20+
Consequently, this indicates where an API should be added! Adding an API at a
21+
particular level in the hierarchy means that it is supported on all the child
22+
platforms of that level. For example, when adding a Unix API it should be added
23+
to `src/unix/mod.rs`, but when adding a Linux-only API it should be added to
24+
`src/unix/linux_like/linux/mod.rs`.
25+
26+
If you're not 100% sure at what level of the hierarchy an API should be added
27+
at, fear not! This crate has CI support which tests any binding against all
28+
platforms supported, so you'll see failures if an API is added at the wrong
29+
level or has different signatures across platforms.
30+
31+
New symbol(s) (i.e. functions, constants etc.) should also be added to the
32+
symbols list(s) found in the `libc-test/semver` directory. These lists keep
33+
track of what symbols are public in the libc crate and ensures they remain
34+
available between changes to the crate. If the new symbol(s) are available on
35+
all supported Unixes it should be added to `unix.txt` list<sup>1</sup>,
36+
otherwise they should be added to the OS specific list(s).
37+
38+
With that in mind, the steps for adding a new API are:
39+
40+
1. Determine where in the module hierarchy your API should be added.
41+
2. Add the API, including adding new symbol(s) to the semver lists.
42+
3. Send a PR to this repo.
43+
4. Wait for CI to pass, fixing errors.
44+
5. Wait for a merge!
45+
46+
<sup>1</sup>: Note that this list has nothing to do with any Unix or Posix
47+
standard, it's just a list shared between all OSs that declare `#[cfg(unix)]`.
48+
49+
## Test before you commit
50+
51+
We have two automated tests running on [GitHub Actions](https://github.com/rust-lang/libc/actions):
52+
53+
1. [`libc-test`](https://github.com/gnzlbg/ctest)
54+
- `cd libc-test && cargo test`
55+
- Use the `skip_*()` functions in `build.rs` if you really need a workaround.
56+
2. Style checker
57+
- `rustc ci/style.rs && ./style src`
58+
59+
## Breaking change policy
60+
61+
Sometimes an upstream adds a breaking change to their API e.g. removing outdated items,
62+
changing the type signature, etc. And we probably should follow that change to build the
63+
`libc` crate successfully. It's annoying to do the equivalent of semver-major versioning
64+
for each such change. Instead, we mark the item as deprecated and do the actual change
65+
after a certain period. The steps are:
66+
67+
1. Add `#[deprecated(since = "", note="")]` attribute to the item.
68+
- The `since` field should have a next version of `libc`
69+
(e.g., if the current version is `0.2.1`, it should be `0.2.2`).
70+
- The `note` field should have a reason to deprecate and a tracking issue to call for comments
71+
(e.g., "We consider removing this as the upstream removed it.
72+
If you're using it, please comment on #XXX").
73+
2. If we don't see any concerns for a while, do the change actually.
74+
75+
## Releasing your change to crates.io
76+
77+
Now that you've done the amazing job of landing your new API or your new
78+
platform in this crate, the next step is to get that sweet, sweet usage from
79+
crates.io! The only next step is to bump the version of libc and then publish
80+
it. If you'd like to get a release out ASAP you can follow these steps:
81+
82+
1. Increment the patch version number in `Cargo.toml` and `libc-test/Cargo.toml`.
83+
1. Send a PR to this repository. It should [look like this][example-pr], but it'd
84+
also be nice to fill out the description with a small rationale for the
85+
release (any rationale is ok though!)
86+
1. Once merged, the release will be tagged and published by one of the libc crate
87+
maintainers.
88+
89+
[example-pr]: https://github.com/rust-lang/libc/pull/2120

‎collector/benchmarks/libc-0.2.124/Cargo.toml

Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
# THIS FILE IS AUTOMATICALLY GENERATED BY CARGO
2+
#
3+
# When uploading crates to the registry Cargo will automatically
4+
# "normalize" Cargo.toml files for maximal compatibility
5+
# with all versions of Cargo and also rewrite `path` dependencies
6+
# to registry (e.g., crates.io) dependencies.
7+
#
8+
# If you are reading this file be aware that the original Cargo.toml
9+
# will likely look very different (and much more reasonable).
10+
# See Cargo.toml.orig for the original contents.
11+
12+
[package]
13+
name = "libc"
14+
version = "0.2.124"
15+
authors = ["The Rust Project Developers"]
16+
build = "build.rs"
17+
exclude = [
18+
"/ci/*",
19+
"/.github/*",
20+
"/.cirrus.yml",
21+
"/triagebot.toml",
22+
]
23+
description = """
24+
Raw FFI bindings to platform libraries like libc.
25+
"""
26+
homepage = "https://github.com/rust-lang/libc"
27+
documentation = "https://docs.rs/libc/"
28+
readme = "README.md"
29+
keywords = [
30+
"libc",
31+
"ffi",
32+
"bindings",
33+
"operating",
34+
"system",
35+
]
36+
categories = [
37+
"external-ffi-bindings",
38+
"no-std",
39+
"os",
40+
]
41+
license = "MIT OR Apache-2.0"
42+
repository = "https://github.com/rust-lang/libc"
43+
44+
[package.metadata.docs.rs]
45+
features = [
46+
"const-extern-fn",
47+
"extra_traits",
48+
]
49+
50+
[dependencies.rustc-std-workspace-core]
51+
version = "1.0.0"
52+
optional = true
53+
54+
[features]
55+
align = []
56+
const-extern-fn = []
57+
default = ["std"]
58+
extra_traits = []
59+
rustc-dep-of-std = [
60+
"align",
61+
"rustc-std-workspace-core",
62+
]
63+
std = []
64+
use_std = ["std"]

‎collector/benchmarks/libc-0.2.124/Cargo.toml.orig

Lines changed: 35 additions & 0 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

‎collector/benchmarks/libc-0.2.124/LICENSE-APACHE

Lines changed: 176 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,176 @@
1+
Apache License
2+
Version 2.0, January 2004
3+
http://www.apache.org/licenses/
4+
5+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6+
7+
1. Definitions.
8+
9+
"License" shall mean the terms and conditions for use, reproduction,
10+
and distribution as defined by Sections 1 through 9 of this document.
11+
12+
"Licensor" shall mean the copyright owner or entity authorized by
13+
the copyright owner that is granting the License.
14+
15+
"Legal Entity" shall mean the union of the acting entity and all
16+
other entities that control, are controlled by, or are under common
17+
control with that entity. For the purposes of this definition,
18+
"control" means (i) the power, direct or indirect, to cause the
19+
direction or management of such entity, whether by contract or
20+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
21+
outstanding shares, or (iii) beneficial ownership of such entity.
22+
23+
"You" (or "Your") shall mean an individual or Legal Entity
24+
exercising permissions granted by this License.
25+
26+
"Source" form shall mean the preferred form for making modifications,
27+
including but not limited to software source code, documentation
28+
source, and configuration files.
29+
30+
"Object" form shall mean any form resulting from mechanical
31+
transformation or translation of a Source form, including but
32+
not limited to compiled object code, generated documentation,
33+
and conversions to other media types.
34+
35+
"Work" shall mean the work of authorship, whether in Source or
36+
Object form, made available under the License, as indicated by a
37+
copyright notice that is included in or attached to the work
38+
(an example is provided in the Appendix below).
39+
40+
"Derivative Works" shall mean any work, whether in Source or Object
41+
form, that is based on (or derived from) the Work and for which the
42+
editorial revisions, annotations, elaborations, or other modifications
43+
represent, as a whole, an original work of authorship. For the purposes
44+
of this License, Derivative Works shall not include works that remain
45+
separable from, or merely link (or bind by name) to the interfaces of,
46+
the Work and Derivative Works thereof.
47+
48+
"Contribution" shall mean any work of authorship, including
49+
the original version of the Work and any modifications or additions
50+
to that Work or Derivative Works thereof, that is intentionally
51+
submitted to Licensor for inclusion in the Work by the copyright owner
52+
or by an individual or Legal Entity authorized to submit on behalf of
53+
the copyright owner. For the purposes of this definition, "submitted"
54+
means any form of electronic, verbal, or written communication sent
55+
to the Licensor or its representatives, including but not limited to
56+
communication on electronic mailing lists, source code control systems,
57+
and issue tracking systems that are managed by, or on behalf of, the
58+
Licensor for the purpose of discussing and improving the Work, but
59+
excluding communication that is conspicuously marked or otherwise
60+
designated in writing by the copyright owner as "Not a Contribution."
61+
62+
"Contributor" shall mean Licensor and any individual or Legal Entity
63+
on behalf of whom a Contribution has been received by Licensor and
64+
subsequently incorporated within the Work.
65+
66+
2. Grant of Copyright License. Subject to the terms and conditions of
67+
this License, each Contributor hereby grants to You a perpetual,
68+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69+
copyright license to reproduce, prepare Derivative Works of,
70+
publicly display, publicly perform, sublicense, and distribute the
71+
Work and such Derivative Works in Source or Object form.
72+
73+
3. Grant of Patent License. Subject to the terms and conditions of
74+
this License, each Contributor hereby grants to You a perpetual,
75+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76+
(except as stated in this section) patent license to make, have made,
77+
use, offer to sell, sell, import, and otherwise transfer the Work,
78+
where such license applies only to those patent claims licensable
79+
by such Contributor that are necessarily infringed by their
80+
Contribution(s) alone or by combination of their Contribution(s)
81+
with the Work to which such Contribution(s) was submitted. If You
82+
institute patent litigation against any entity (including a
83+
cross-claim or counterclaim in a lawsuit) alleging that the Work
84+
or a Contribution incorporated within the Work constitutes direct
85+
or contributory patent infringement, then any patent licenses
86+
granted to You under this License for that Work shall terminate
87+
as of the date such litigation is filed.
88+
89+
4. Redistribution. You may reproduce and distribute copies of the
90+
Work or Derivative Works thereof in any medium, with or without
91+
modifications, and in Source or Object form, provided that You
92+
meet the following conditions:
93+
94+
(a) You must give any other recipients of the Work or
95+
Derivative Works a copy of this License; and
96+
97+
(b) You must cause any modified files to carry prominent notices
98+
stating that You changed the files; and
99+
100+
(c) You must retain, in the Source form of any Derivative Works
101+
that You distribute, all copyright, patent, trademark, and
102+
attribution notices from the Source form of the Work,
103+
excluding those notices that do not pertain to any part of
104+
the Derivative Works; and
105+
106+
(d) If the Work includes a "NOTICE" text file as part of its
107+
distribution, then any Derivative Works that You distribute must
108+
include a readable copy of the attribution notices contained
109+
within such NOTICE file, excluding those notices that do not
110+
pertain to any part of the Derivative Works, in at least one
111+
of the following places: within a NOTICE text file distributed
112+
as part of the Derivative Works; within the Source form or
113+
documentation, if provided along with the Derivative Works; or,
114+
within a display generated by the Derivative Works, if and
115+
wherever such third-party notices normally appear. The contents
116+
of the NOTICE file are for informational purposes only and
117+
do not modify the License. You may add Your own attribution
118+
notices within Derivative Works that You distribute, alongside
119+
or as an addendum to the NOTICE text from the Work, provided
120+
that such additional attribution notices cannot be construed
121+
as modifying the License.
122+
123+
You may add Your own copyright statement to Your modifications and
124+
may provide additional or different license terms and conditions
125+
for use, reproduction, or distribution of Your modifications, or
126+
for any such Derivative Works as a whole, provided Your use,
127+
reproduction, and distribution of the Work otherwise complies with
128+
the conditions stated in this License.
129+
130+
5. Submission of Contributions. Unless You explicitly state otherwise,
131+
any Contribution intentionally submitted for inclusion in the Work
132+
by You to the Licensor shall be under the terms and conditions of
133+
this License, without any additional terms or conditions.
134+
Notwithstanding the above, nothing herein shall supersede or modify
135+
the terms of any separate license agreement you may have executed
136+
with Licensor regarding such Contributions.
137+
138+
6. Trademarks. This License does not grant permission to use the trade
139+
names, trademarks, service marks, or product names of the Licensor,
140+
except as required for reasonable and customary use in describing the
141+
origin of the Work and reproducing the content of the NOTICE file.
142+
143+
7. Disclaimer of Warranty. Unless required by applicable law or
144+
agreed to in writing, Licensor provides the Work (and each
145+
Contributor provides its Contributions) on an "AS IS" BASIS,
146+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147+
implied, including, without limitation, any warranties or conditions
148+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149+
PARTICULAR PURPOSE. You are solely responsible for determining the
150+
appropriateness of using or redistributing the Work and assume any
151+
risks associated with Your exercise of permissions under this License.
152+
153+
8. Limitation of Liability. In no event and under no legal theory,
154+
whether in tort (including negligence), contract, or otherwise,
155+
unless required by applicable law (such as deliberate and grossly
156+
negligent acts) or agreed to in writing, shall any Contributor be
157+
liable to You for damages, including any direct, indirect, special,
158+
incidental, or consequential damages of any character arising as a
159+
result of this License or out of the use or inability to use the
160+
Work (including but not limited to damages for loss of goodwill,
161+
work stoppage, computer failure or malfunction, or any and all
162+
other commercial damages or losses), even if such Contributor
163+
has been advised of the possibility of such damages.
164+
165+
9. Accepting Warranty or Additional Liability. While redistributing
166+
the Work or Derivative Works thereof, You may choose to offer,
167+
and charge a fee for, acceptance of support, warranty, indemnity,
168+
or other liability obligations and/or rights consistent with this
169+
License. However, in accepting such obligations, You may act only
170+
on Your own behalf and on Your sole responsibility, not on behalf
171+
of any other Contributor, and only if You agree to indemnify,
172+
defend, and hold each Contributor harmless for any liability
173+
incurred by, or claims asserted against, such Contributor by reason
174+
of your accepting any such warranty or additional liability.
175+
176+
END OF TERMS AND CONDITIONS

0 commit comments

Comments
 (0)