cortex-gnat-rts
gcc
Our great sponsors
cortex-gnat-rts | gcc | |
---|---|---|
7 | 81 | |
60 | 8,732 | |
- | 2.2% | |
2.7 | 9.9 | |
about 1 year ago | 1 day ago | |
Ada | C | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cortex-gnat-rts
-
Writing Startup Code for STM32 in Completely Ada
Also, u/simonjwright 's cortex-gnat-rts was most helpful.
-
Define project-wide allocator on bare application.
You could look at providing your own version of System.Memory - this was easy enough in an embedded system with a restricted runtime, but much hairier in full Ada.
-
Ada on ESP32 and FreeRTOS
It includes a customized GNAT RunTime (besed on cortex-gnat-rts) and a ESP32 toolchain binaries. It's integrated in Espressif IoT Development Framework build system.
-
Clarification on Finalization
I looked into finalization without exceptions for Cortex GNAT RTS, branch finalization, not touched since 2018; not too difficult (largely reinstating stuff I’d cut out because of restriction No_Finalization).
-
Spunky (Kernel written in Ada) #4: Kernel Timing
What I had in mind was the usage generated by AdaCore’s SVD2Ada, e.g. the register without the pragma, and the place in the wider data structure in which it’s used, with the pragma.
-
Array copies on bare metal using GNU GNAT generate library calls
This code, which I unthinkingly wrote thinking "how clever!", in fact calls memcpy() and memset() under the hood, which works because the compiler was built including Newlib.
-
Please explain secondary stack to a C programmer!
.. and a simple version here.
gcc
-
C++ Safety, in Context
> It's true, this was a CVE in Rust and not a CVE in C++, but only because C++ doesn't regard the issue as a problem at all. The problem definitely exists in C++, but it's not acknowledged as a problem, let alone fixed.
Can you find a link that substantiates your claim? You're throwing out some heavy accusations here that don't seem to match reality at all.
Case in point, this was fixed in both major C++ libraries:
https://github.com/gcc-mirror/gcc/commit/ebf6175464768983a2d...
https://github.com/llvm/llvm-project/commit/4f67a909902d8ab9...
So what C++ community refused to regard this as an issue and refused to fix it? Where is your supporting evidence for your claims?
- Std: Clamp generates less efficient assembly than std:min(max,std:max(min,v))
-
Converting the Kernel to C++
Somewhat related: In 2020 gcc bumped the requirement for bootstrapping to be a C++11 compiler [0]. Would have been fun to see the kernel finally adopt C++14 as the author suggested.
I don't think that Linus will allow this since he just commented that he will allow rust in drivers and major subsystems [1].
I do found it pretty funny that even Linus is also not writing any rust code, but is reading rust code.
I would have hoped see more answers or see something in here from actual kernel developers.
0: https://github.com/gcc-mirror/gcc/commit/5329b59a2e13dabbe20...
-
Understanding Objective-C by transpiling it to C++
> They’re saying that a lot of the restrictions makes things much harder than other languages. Hence the general problem rust has where a lot of trivial tasks in other languages are extremely challenging.
Like what? So far the discussion has revolved around rewriting a linked list, which people generally shouldn't ever need to do because it's included in the standard lib for most languages. And it's a decidedly nontrivial task to do as well as the standard lib when you don't sacrifice runtime overhead to be able to handwave object lifecycle management.
- C++: https://github.com/gcc-mirror/gcc/blob/master/libstdc%2B%2B-...
- Rust: https://doc.rust-lang.org/beta/src/alloc/collections/linked_...
> No need to get defensive, no one is arguing that rust doesn’t do a lot of things well.
That's literally what bsaul is arguing in another comment. :)
> You’re talking up getting a safe implementation in C, but what matters is “can I get the same level of safety with less complexity in any language”, and the answer is yes: Java and c# implementations of a thread safe linked list are trivial.
Less perceived complexity. In Java and C# you're delegating the responsibility of lifecycle management to garbage collectors. For small to medium scale web apps, the added complexity will be under the hood and you won't have to worry about it. For extreme use cases, the behavior and overhead of the garbage collector does became relevant.
If you factor in the code for the garbage collector that Java and C# depend on, the code complexity will tilt dramatically in favor of C++ or Rust.
However, it's going to be non-idiomatic to rewrite a garbage collector in Java or C# like it is to rewrite a linked list in Rust. If we consider the languages as they're actually used, rather than an academic scenario which mostly crops up when people expect the language to behave like C or Java, the comparison is a lot more favorable than you're framing it as.
> If I wanted I could do it in c++ though the complexity would be more than c# and Java it would be easier than rust.
You can certainly write a thread-safe linked list in C++, but then the enforcement of any assumptions you made about using it will be a manual burden on the user. This isn't just a design problem you can solve with more code - C++ is incapable of expressing the same restrictions as Rust, because doing so would break compatibility with C++ code and the language constructs needed to do so don't exist.
So it's somewhat apples and oranges here. Yes, you may have provided your team with a linked list, but it will either
-
Committing to Rust for Kernel Code
GCC is also written in C++, and has had C++ deps since 2013:
https://github.com/gcc-mirror/gcc/blob/master/gcc/c/c-parser...
- Spitbol 360: an implementation of SNOBOL4 for IBM 360 compatible computers
-
are most computer programming languages public domain, or do their creators get a say in what you do with them?
Compliers/Interpreters are also very commonly open source (here is the source code for a popular C compiler). That means you can even modify the compiler's code and change its behavior if you wanted to.
- Learn to write production quality STL like classes
-
Which compiler is conforming here?
according to this commit, the story here seems to be much more interessting than I initially anticipated.
-
My favorite C compiler flags during development
For a more detailed explanation, see [2]. (Also the inspiration for the above example,)
[1] https://en.m.wikipedia.org/wiki/Transitive_relation
[2] https://github.com/gcc-mirror/gcc/commit/50ddbd0282e06614b29...
What are some alternatives?
esp32-gnat-rts - This project contains various GNAT Ada Run Time Systems (RTSs) targeted at Cortex boards: so far, the Arduino Due, the STM32F4-series evaluation boards from STMicroelectronics, and the BBC micro:bit
CMake - Mirror of CMake upstream repository
svd2ada - An Ada binding generator from SVD descriptions for bare board ARM devices.
rtl8192eu-linux-driver - Drivers for the rtl8192eu chipset for wireless adapters (D-Link DWA-131 rev E1 included!)
Ada_Drivers_Library - Ada source code and complete sample GNAT projects for selected bare-board platforms supported by GNAT.
llvm-project - The LLVM Project is a collection of modular and reusable compiler and toolchain technologies.
ada-spark-rfcs - Platform to submit RFCs for the Ada & SPARK languages
STL - MSVC's implementation of the C++ Standard Library.
bingada - Bingo application in GTKAda
cobol-on-wheelchair - Micro web-framework for COBOL
ada-spark-rfcs - Platform to submit RFCs for the Ada & SPARK languages
busybox - The Swiss Army Knife of Embedded Linux - private tree