<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rust/library/std/src/sys/solid/fs.rs, branch 1.63.0</title>
<subtitle>https://github.com/rust-lang/rust
</subtitle>
<id>http://git.dreamy.place/mirrors/rust/atom?h=1.63.0</id>
<link rel='self' href='http://git.dreamy.place/mirrors/rust/atom?h=1.63.0'/>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/'/>
<updated>2022-02-10T04:33:35+00:00</updated>
<entry>
<title>kmc-solid: Use the filesystem thread-safety wrapper</title>
<updated>2022-02-10T04:33:35+00:00</updated>
<author>
<name>Tomoaki Kawada</name>
<email>kawada@kmckk.co.jp</email>
</author>
<published>2022-02-10T04:10:25+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=64406c5996a0775493c8a2acd457e612bd84cde6'/>
<id>urn:sha1:64406c5996a0775493c8a2acd457e612bd84cde6</id>
<content type='text'>
Neither the SOLID filesystem API nor built-in filesystems guarantee
thread safety by default. Although this may suffice in general embedded-
system use cases, and in fact the API can be used from multiple threads
without any problems in many cases, this has been a source of
unsoundness in `std::sys::solid::fs`.

This commit updates the `std` code to leverage the filesystem thread-
safety wrapper to enforce thread safety. This is done by prefixing all
paths passed to the filesystem API with `\TS`. (Note that relative paths
aren't supported in this platform.)
</content>
</entry>
<entry>
<title>Hide Repr details from io::Error, and rework `io::Error::new_const`.</title>
<updated>2022-02-05T02:47:29+00:00</updated>
<author>
<name>Thom Chiovoloni</name>
<email>chiovolonit@gmail.com</email>
</author>
<published>2021-08-08T08:04:33+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=554918e311a1221744aa9b6d60e2f00f5b3155e5'/>
<id>urn:sha1:554918e311a1221744aa9b6d60e2f00f5b3155e5</id>
<content type='text'>
</content>
</entry>
<entry>
<title>kmc-solid: Add `std::sys::solid::fs::File::read_buf`</title>
<updated>2021-12-21T02:18:35+00:00</updated>
<author>
<name>Tomoaki Kawada</name>
<email>kawada@kmckk.co.jp</email>
</author>
<published>2021-12-20T05:20:48+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=874514c7b4f58256eb1c9fe4c9903cdb9e09cada'/>
<id>urn:sha1:874514c7b4f58256eb1c9fe4c9903cdb9e09cada</id>
<content type='text'>
Catching up with commit 3b263ceb5cb89b6d53b5a03b47ec447c3a7f7765
</content>
</entry>
<entry>
<title>Add SOLID targets</title>
<updated>2021-09-28T02:31:47+00:00</updated>
<author>
<name>Tomoaki Kawada</name>
<email>kawada@kmckk.co.jp</email>
</author>
<published>2021-09-28T02:20:46+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=da9ca41c318aadcc0a9e8f72f86c1d36c8fe6d5d'/>
<id>urn:sha1:da9ca41c318aadcc0a9e8f72f86c1d36c8fe6d5d</id>
<content type='text'>
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/
</content>
</entry>
</feed>
