|
01:01
guifa joined
02:32
guifa left
|
|||
| ShimmerFairy | timo: Looks like it's used by tools/check.mk, which can be invoked with the clangcheck and gcccheck targets. Not sure what it's for, but presumably it's some kind of way of doing extra checking with compilers, but gcccheck immediately fails for me because I don't have mimalloc installed. | 04:25 | |
| Yeah, it's just for checking the files with extra checks, for example for GCC it runs `gcc -fsyntax-only -std=c99 -Werror -Wall -Wextra` (the -fsyntax-only meaning it doesn't actually compile anything). As currently set up this ends up being kinda worthless, since it immediately dies on all the unused parameters (which you couldn't portably mark as intentional until C23). | 04:31 | ||
| Trying to make use of check.mk, it seems like a really bad approach to running a stricter compiler. I keep running into issues with the check.mk file either being out-of-date with current practices, or not understanding my actual build configuration (e.g. trying to build libffi-based nativecall when I didn't configure for it, and when I do it fails because of a missing -I for libffi) | 04:52 | ||
|
05:46
JimmyZhuo joined
|
|||
| JimmyZhuo | timo: used by 'gmake gcccheck', or clangcheck | 05:48 | |
| commit 5027db8ca01cfcf1936e312fc50505d4ab0b7a99 | |||
| Author: Gerhard R <gerd.r.devel@googlemail.com> | |||
| Date: Tue Aug 27 21:15:19 2013 +0200 | |||
| Implement clangcheck and gcccheck make targets | |||
|
05:53
JimmyZhuo left
14:15
guifa joined
|
|||
| timo | we should feed a build of moarvm into coverity scan again | 15:07 | |
| lizmat | what would be needed for that ? | 15:08 | |
| timo | really, i just need to invest a few minutes | 15:09 | |
| remember travis-ci | 15:11 | ||
| i'll have a build to submit soon | 15:17 | ||
| > Last Build Status: In-queue. Your build is in the queue to be analyzed. There are 2 builds ahead of it. | 15:27 | ||
| > Sep 07, 2022 Last Analyzed | 15:28 | ||
| scan.coverity.com/projects/paultcochrane-moarvm - i'm not sure if just anybody can open the defects viewer or if you need to log in to this site with an account first | 15:34 | ||
|
15:53
guifa left
|
|||
| Geth | MoarVM/event_loop_started_status_without_mutex: f4e5a0a78f | (Timo Paulssen)++ | 6 files Use atomic instead of mutex for "is event loop started" The theory is that reading an atomic that only very rarely changes is cheaper than locking and unlocking a mutex for reading. Coverity Scan pointed out in CID 501093 that another thread could see instance->event_loop_thread become nonzero before the other field writes would be complete, thus causing a data race. ... (6 more lines) |
17:18 | |
| MoarVM/event_loop_started_status_without_mutex: f8c251c6d3 | (Timo Paulssen)++ | 6 files Use atomic instead of mutex for "is event loop started" The theory is that reading an atomic that only very rarely changes is cheaper than locking and unlocking a mutex for reading. Coverity Scan pointed out in CID 501093 that another thread could see instance->event_loop_thread become nonzero before the other field writes ... (11 more lines) |
17:19 | ||
|
19:10
lizmat joined,
Geth joined
|
|||
| Geth | MoarVM/event_loop_started_status_without_mutex: 30c938d96c | (Timo Paulssen)++ | 4 files telemeh: make forks visible, continue working after fork |
19:20 | |
| MoarVM/timo_january_2026_coverityscan: 5 commits pushed by (Timo Paulssen)++ | 19:21 | ||
|
23:22
guifa joined
|
|||