Skip to content

Commit 230b8e1

Browse files
committed
devlog
1 parent d247cb3 commit 230b8e1

File tree

1 file changed

+29
-5
lines changed

1 file changed

+29
-5
lines changed

DEVLOG.md

+29-5
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,31 @@
11
# devlog
22

3+
## Sun June 16, 2024
4+
5+
### nlnet updates
6+
7+
After some back and for with @jimblandy on my second PR I've landed on a set of changes that
8+
actually produce a validating `naga::Module`! That means the system is producing viable code!
9+
10+
What this means is that I'm actually very close to hitting the first nlnet milestone!
11+
12+
With that, I've started work on the second milestone while my first set of PRs are in review,
13+
as it takes a good while to roundtrip w/ feedback.
14+
15+
### raspberry pi updates
16+
17+
Still getting OOM errors and I'm not sure why. There are a few changes I need to make to figure
18+
it out:
19+
20+
- [ ] env var configurable logging in tests
21+
* because we need to be able to debug where the memory is going
22+
- [ ] add a new test that ensures the image comparison machinery is sane
23+
* because the comparisons seem pretty borked
24+
325
## Fri June 14, 2024
426

27+
### nlnet updates
28+
529
I put up [another incremental PR for `naga`'s SPIR-V frontend](https://github.com/gfx-rs/wgpu/pull/5775)
630
that applies atomic upgrades to types and to a lesser extent to expressions. It's currently awaiting
731
review from @jimblandy. If I'm still on-point and understanding the direction then I'll be adding the
@@ -13,17 +37,17 @@ therefore after an expression upgrade we need to traverse the `Module` looking f
1337
references and upgrade the expressions that contains them - which then must be iterated upon
1438
again, searching the `Module` for expressions that may contain _those_ as sub-expressions.
1539

16-
I do have a couple questions that I'm purposefully *not* addressing yet:
17-
18-
* TODO
19-
2040
## Sun June 9, 2024
2141

42+
### nlnet updates
43+
2244
Following @jimblandy's advice I've got a good portion of the atomic "upgrade" process working.
2345
* [@jimblandy's explaination of steps required](https://app.element.io/#/room/#naga:matrix.org/$eIqQA71wsmmzR0NWug4KsSFk3YKiX8zpIG6ToNN-0Sk)
2446

2547
## Tue June 4, 2024
2648

49+
### nlnet updates
50+
2751
I'm working on "upgrading" pointer types in `naga`'s SPIR-V frontend. This really is the meat of the
2852
problem, I would say. I'm attempting to follow this process, roughly:
2953

@@ -76,7 +100,7 @@ I posted this on the `wgpu`/`naga` matrix and @jimblandy [replied here](https://
76100

77101
## Mon June 3, 2024
78102

79-
### NLNet progress
103+
### nlnet updates
80104

81105
[My first PR to add atomics to naga's SPIR-V frontend](https://github.com/gfx-rs/wgpu/pull/5702) was
82106
merged last week! I'm super stoked because I was worried it might be a bit beyond my pay grade, but

0 commit comments

Comments
 (0)