User Details
- User Since
- May 11 2018, 1:45 AM (281 w, 1 d)
Yesterday
Rebase
Make changes requested by @ldionne and rebase.
Thu, Sep 28
Ping
Ping
Wed, Sep 20
Tue, Sep 19
Rebase
Rebase
Mon, Sep 11
Aug 16 2023
Aug 11 2023
Aug 9 2023
Aug 3 2023
Aug 2 2023
Hi Sam, I won't be able to take this forward but you have my encouragement. To facilitate this change I got as far as changing Git [1], and GitHub has been updated accordingly [2], but I ran out of steam before getting to the change itself.
I'd be happy to let someone else (you?) take the lead and commandeer the change.
Jul 27 2023
LGTM
Jul 24 2023
some nasty and repetitive regexes
Jul 20 2023
Jul 19 2023
OK if I get any more review comments I'll do that. The new "Armv7-M picolibc" configuration is passing in BuildKite now and the failures in other configurations look unrelated so I have no changes planned at this point.
Rebase after -Wcast-qual error was fixed
Rebase after -Wcast-qual error was fixed
LGTM and fixes the issue for me. I agree there doesn't seem to be a good reason to have the const there in the first place.
Handle command line arguments
atomics -> has-64-bit-atomics
Jul 18 2023
LGTM but please allow a day for others to comment.
Use 16MB area of RAM to enable running bigger tests
Use 16MB area of RAM to enable running bigger tests
Move code to find qemu-system-arm program
Change how atomics feature is detected and change atomic REQUIRES back to negated XFAIL
Jul 17 2023
XFAIL: !atomics -> REQUIRES: atomics
Add "atomics" feature, run git-clang-format, and other minor tweaks
@lhames ping
Jul 14 2023
Hi Joe, it's nice to see multilib.yaml getting some adoption :)
Compile and link tests
Jul 13 2023
Jul 12 2023
Jul 11 2023
Jul 10 2023
Add summary comment to build-picolibc.sh
LGTM
Jul 7 2023
Jul 6 2023
Default to compiling picolibc with cc
clang -> $CC
Thanks for this, LGTM.
Fix duplicate implicit group warning
Jul 4 2023
The fixes building with picolibc, thanks!
With these changes, copied from chrono.cpp, this patch fixes building with picolibc.
Does that mean the platform doesn't provide a way to check the time, or is it that the API it provides is just different? How is e.g. std::system_clock implemented on that platform?
Apply @ldionne's suggestions
Jul 3 2023
send error messages to stderr
Apply review suggestions
Jun 30 2023
Jun 29 2023
Jun 28 2023
Jun 27 2023
Rename variable
Jun 26 2023
LGTM
The change seems OK to me in principle, but I'd appreciate the code being more self-descriptive. Thanks.
Jun 23 2023
Tweak warning message
Jun 22 2023
<input triple> selects the fallback GCC toolchain driver; did you mean <proposed triple>
This is a correct description of the current behaviour, but I want to keep the freedom to change the behaviour in future. Therefore I'd like to avoid defining what behaviour an invalid target triple will cause.