Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
gingerBill
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
Casey Muratori – The Root of the Root of All Evil – BSC 2026 [video]
(youtube.com)
16 points
by
gingerBill
22d ago
|
1 comments
2.
▲
by
gingerBill
24d ago
> No, you have tables _of the instructions that the compiler codegen may use_. That's a distinction without a difference. > ...because for most architectures it may not even be possible to build such tables in the first place!. N
3.
▲
by
gingerBill
24d ago
That "trick" is just a fancy string effectively, the thing I am complaining about in the first part of the article. And that little secret really does mean it is a fancy string again. I did not want any of that for any reason.
4.
▲
by
gingerBill
24d ago
1. I don't think I am overselling rexcode, rather there isn't anything like it in the first place as a single library with that many ISAs and IRs. That's what I love about it, since I can now trivially make (non-optimizing) c
5.
▲
by
gingerBill
25d ago
I haven't fully thought out that syntax yet, but it's a problem with AVX-512 in terms of its predicate operands too. My hunch would be the following: sve_ld1d_scalar :: asm(base: [^]u64, idx: i64, #mask pred: u16) ->
6.
▲
by
gingerBill
25d ago
How is this not an assembler?—even with your description which matches an assembler to a tee. It genuinely is an assembler, and I am not sure how you are thinking otherwise. And where is the AT&T? Did you even look at the syntax or read
7.
▲
by
gingerBill
25d ago
Odin is never going to support SHARC nor Hexagon, so it is literally not a problem. And I do not even seen why a universal syntax for such ISAs is impossible to support either at the syntax level. Hexagon's `.new`/`:sat`/`:&l
8.
▲
by
gingerBill
25d ago
> It supports x86, too Well I assumed so because amd64 is a superset of x86. But nice to know you're working on arm64 too. Regarding Intel-syntax, I think there is a little miscommunication here since I try to explain what I mean in
9.
▲
by
gingerBill
25d ago
Why is a bad thing that another language design and compiler writer compares his language as a point of comparison? I really like it when he does because it allows me to see what he has done for D, and learn from it.
10.
▲
by
gingerBill
25d ago
D's approach is great, but it has a few limitations for my use case in Odin. It only supports x86_64/amd64 and uses Intel-style syntax, whereas I needed a solution that universalizes its syntax across multiple ISAs. D's inlin
11.
▲
by
gingerBill
25d ago
That's pretty much the quibble. Most people's narrow view of type system. And we already track all of the basic side-effects and clobbering that each form of each mnemonic does. That's kind of the entire point of this being p
12.
▲
by
gingerBill
25d ago
> the different operand sizes have a lot of side effects Which we have massive tables for each form which track those side effects and clobbering information too. > author/LLM I am the author, and not an LLM. > Tomorrow you ne
13.
▲
by
gingerBill
27d ago
I know that "untyped" means a single-type, but assembly operands have multiple different kinds of types (as I state in the article). What makes it really interesting is what you can know about each instruction and what it does (wh
14.
▲
by
gingerBill
27d ago
The equivalent Odin syntax looks like this: add_three :: asm(my_in: u64) -> (my_out: u64) { add my_out, my_in, 3 } out_var = add_three(in_var) Which is already infinitely more readable and requires no parochial sigils nor the arcane
15.
▲
by
gingerBill
27d ago
TALs are not what I am referring to here. I am arguing that assembly is already typed and does not need extra annotation to be typed. TALs are also solving an entirely different problem.
16.
▲
Odin's New Inline Assembly Templates
(odin-lang.org)
3 points
by
gingerBill
29d ago
|
0 comments
17.
▲
by
gingerBill
2mo ago
> STM32 microcontroller The answer is "yes" depending on what you mean by STM32 :D But if it's one we don't currently support officially, it should be pretty easy to support too, with probably a little extra assembly.
18.
▲
by
gingerBill
2mo ago
Vim does not have multiple cursors which can be placed ANYWHERE even multiple on the same line and at any offset. You are clearly not aware of what Vim actually offers.
19.
▲
by
gingerBill
2mo ago
> People don't use vim because they enjoy puzzle solving. I didn't say that either nor even imply it, and you know that when you quote me afterwards. So huh?!?! > People don't use Linux because they enjoy tweaking confi
20.
▲
by
gingerBill
2mo ago
> You just edit as normal while recording, and replay those edits later. And there is the problem. The first time you do the edit, it might be fine, but when you make a mistake in the edit, you then have to go back and correct all of the
21.
▲
by
gingerBill
2mo ago
Which is kind of what I was arguing. Understand that having "fun" is not necessarily equivalent to being "productive". And even by an individuals own standards, the two can be completely different. If you are having fun,
22.
▲
by
gingerBill
2mo ago
> The things about multiple cursors is that you think about the processing while doing it That visual feedback is EXTREMELY useful because I learn of the edge cases to what I am editing in bulk (usually formatting code or tables or whate
23.
▲
by
gingerBill
2mo ago
> Sublime is invisible to him because he's been at it for fifteen years. It's not perfect and the bugs that have been there for years (and won't be fixed) have annoyed me for years too. The reason I still stick to Sublime
24.
▲
by
gingerBill
2mo ago
That's not what I was saying. I used vim macros specifically as an example, not Vim as a whole. > I’ve had people tell me how “fun” it was to build a macro to handle some one-off text-refactoring problem. But when I looked at what t
25.
▲
by
gingerBill
2mo ago
> I am afraid the author confuses familiarity with proof that his tools are better. Literally NOT what I was implying or even said anywhere. Quote me where I said anything like that. To quote myself: > What baffles me is that so many
26.
▲
by
gingerBill
2mo ago
Regarding the implementation of Odin's `context` not being thread-local, source from here: https://www.gingerbill.org/article/2025/12/15/odins-most-mis... Another common question I’ve gotten a few t
27.
▲
Blessed Syntax and Ergonomics
(gingerbill.org)
1 points
by
gingerBill
5mo ago
|
0 comments
28.
▲
by
gingerBill
5mo ago
If you're referring to me, I don't use Reddit much at all any more. I used to comment sometimes on that specific subreddit, but I didn't find the community that great nor the conversations that useful for me. There seemed to
29.
▲
by
gingerBill
7mo ago
The categorizes are useful for understand how people perceive a language. It's a human psychology category, and just because you think it is "irrelevant" misunderstands why I made the categorical distinctions in the first pla
30.
▲
by
gingerBill
7mo ago
This might might sound weird but I think that's a distinction without a difference. Those "newline tokens" are effectively the equivalent to a semicolon in the parser. They are statement terminators. The way that Odin or Pyth
More ›