rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2024-01-11	std: begin moving platform support modules into `pal`	joboet	-97/+0

2023-09-01	kmc-solid: Directly delegate to `net::is_interrupted` in ↵	Tomoaki Kawada	-1/+1
	`std::sys::solid::is_interrupted`
2023-08-25	Add a new helper to avoid calling io::Error::kind	Ben Kimock	-0/+5

2022-12-31	std: use id-based thread parking on SOLID	joboet	-2/+2

2022-08-28	Support `#[unix_sigpipe = "inherit\|sig_dfl\|sig_ign"]` on `fn main()`	Martin Nordholts	-1/+1
	This makes it possible to instruct libstd to never touch the signal handler for `SIGPIPE`, which makes programs pipeable by default (e.g. with `./your-program \| head -n 1`) without `ErrorKind::BrokenPipe` errors.
2022-07-25	Rollup merge of #95916 - solid-rs:feat-kmc-solid-abort, r=Mark-Simulacrum	Yuki Okushi	-13/+2
	kmc-solid: Use `libc::abort` to abort a program This PR updates the target-specific abort subroutine for the [`-kmc-solid_`](https://doc.rust-lang.org/nightly/rustc/platform-support/kmc-solid.html) Tier 3 targets. The current implementation uses a `hlt` instruction, which is the most direct way to notify a connected debugger but is not the most flexible way. This PR changes it to call the `abort` libc function, making it possible for a system designer to override its behavior as they see fit.
2022-05-18	std: use an event flag based thread parker on SOLID	joboet	-0/+2

2022-04-14	library: Remove definitions and reexports of `strlen` from libstd	Vadim Petrochenkov	-2/+0

2022-04-11	kmc-solid: Use `abort` to abort a program	Tomoaki Kawada	-13/+2
	The current implementation uses a `hlt` instruction, which is the most direct way to notify a connected debugger but is not the most flexible way. This commit changes it to a call to the `abort` libc function, making it possible for a system designer to override its behavior as they see fit.
2022-03-22	Move std::sys::{mutex, condvar, rwlock} to std::sys::locks.	Mara Bos	-2/+9

2022-03-10	Use implicit capture syntax in format_args	T-O-R-U-S	-1/+1
	This updates the standard library's documentation to use the new syntax. The documentation is worthwhile to update as it should be more idiomatic (particularly for features like this, which are nice for users to get acquainted with). The general codebase is likely more hassle than benefit to update: it'll hurt git blame, and generally updates can be done by folks updating the code if (and when) that makes things more readable with the new format. A few places in the compiler and library code are updated (mostly just due to already having been done when this commit was first authored).
2022-02-04	Hide Repr details from io::Error, and rework `io::Error::new_const`.	Thom Chiovoloni	-2/+2

2021-09-28	Add SOLID targets	Tomoaki Kawada	-0/+96
	SOLID[1] is an embedded development platform provided by Kyoto Microcomputer Co., Ltd. This commit introduces a basic Tier 3 support for SOLID. # New Targets The following targets are added: - `aarch64-kmc-solid_asp3` - `armv7a-kmc-solid_asp3-eabi` - `armv7a-kmc-solid_asp3-eabihf` SOLID's target software system can be divided into two parts: an RTOS kernel, which is responsible for threading and synchronization, and Core Services, which provides filesystems, networking, and other things. The RTOS kernel is a μITRON4.0[2][3]-derived kernel based on the open-source TOPPERS RTOS kernels[4]. For uniprocessor systems (more precisely, systems where only one processor core is allocated for SOLID), this will be the TOPPERS/ASP3 kernel. As μITRON is traditionally only specified at the source-code level, the ABI is unique to each implementation, which is why `asp3` is included in the target names. More targets could be added later, as we support other base kernels (there are at least three at the point of writing) and are interested in supporting other processor architectures in the future. # C Compiler Although SOLID provides its own supported C/C++ build toolchain, GNU Arm Embedded Toolchain seems to work for the purpose of building Rust. # Unresolved Questions A μITRON4 kernel can support `Thread::unpark` natively, but it's not used by this commit's implementation because the underlying kernel feature is also used to implement `Condvar`, and it's unclear whether `std` should guarantee that parking tokens are not clobbered by other synchronization primitives. # Unsupported or Unimplemented Features Most features are implemented. The following features are not implemented due to the lack of native support: - `fs::File::{file_attr, truncate, duplicate, set_permissions}` - `fs::{symlink, link, canonicalize}` - Process creation - Command-line arguments Backtrace generation is not really a good fit for embedded targets, so it's intentionally left unimplemented. Unwinding is functional, however. ## Dynamic Linking Dynamic linking is not supported. The target platform supports dynamic linking, but enabling this in Rust causes several problems. - The linker invocation used to build the shared object of `std` is too long for the platform-provided linker to handle. - A linker script with specific requirements is required for the compiled shared object to be actually loadable. As such, we decided to disable dynamic linking for now. Regardless, the users can try to create shared objects by manually invoking the linker. ## Executable Building an executable is not supported as the notion of "executable files" isn't well-defined for these targets. [1] https://solid.kmckk.com/SOLID/ [2] http://ertl.jp/ITRON/SPEC/mitron4-e.html [3] https://en.wikipedia.org/wiki/ITRON_project [4] https://toppers.jp/