Personal channel of @lancern
Topics: programming, hacking, memes, life, and more. Forward anything as you wish.
Join the discussion group for more fun.
Discord: https://discord.gg/RwUx9et7
Topics: programming, hacking, memes, life, and more. Forward anything as you wish.
Join the discussion group for more fun.
Discord: https://discord.gg/RwUx9et7
https://openai.com/index/learning-to-reason-with-llms/
Openai
Learning to reason with LLMs
We are introducing OpenAI o1, a new large language model trained with reinforcement learning to perform complex reasoning. o1 thinks before it answers—it can produce a long internal chain of thought before responding to the user.
GFW 改变干扰 Docker 官方安装脚本域名方式
有消息¹称当前 get.docker.com 和 download.docker.com 中国大陆可以直连。但经测试，首次可以正常访问，但会重置后续连接，并不是真正停止干扰，这么做可能只是为了营造网络不稳定的假相，与干扰 GitHub 的方式类似。
Docker Hub 域名 hub.docker.com 依然完全无法直连。（本文有更新）
—— [1] V2EX
有消息¹称当前 get.docker.com 和 download.docker.com 中国大陆可以直连。但经测试，首次可以正常访问，但会重置后续连接，并不是真正停止干扰，这么做可能只是为了营造网络不稳定的假相，与干扰 GitHub 的方式类似。
Docker Hub 域名 hub.docker.com 依然完全无法直连。（本文有更新）
—— [1] V2EX
A ToC of the 20 part linker essay
https://lwn.net/Articles/276782/
https://lwn.net/Articles/276782/
再见了，盛夏 - Airing 的博客
https://blog.ursb.me/posts/2024-summer/
https://blog.ursb.me/posts/2024-summer/
Programming Zero Knowledge Proofs: From Zero to Hero https://zkintro.com/articles/programming-zkps-from-zero-to-hero
zkintro
Programming ZKPs: From Zero to Hero
Learn to write and modify Zero Knowledge Proofs from scratch. You'll build a digital signature scheme using hash-based commitments, gaining practical ZKP programming skills and intuition along the way. By the end, you'll have all the tools you need to implement…
Cascadia 字体推出了官方的 CJK 1:2 版本！
https://github.com/microsoft/cascadia-code/releases/tag/cascadia-next
图片
https://github.com/microsoft/cascadia-code/releases/tag/cascadia-next
图片
Erasure Coding for Distributed Systems https://transactional.blog/blog/2024-erasure-coding
Intel SGX Fuse Key0, a.k.a. Root Provisioning Key Was Extracted by Researchers https://twitter.com/_markel___/status/1828112469010596347
X (formerly Twitter)
Mark Ermolov (@_markel___) on X
Intel HW is too complex to be absolutely secure! After years of research we finally extracted Intel SGX Fuse Key0, AKA Root Provisioning Key. Together with FK1 or Root Sealing Key (also compromised), it represents Root of Trust for SGX. Here's the key from…
为什么会发现这个，是因为咱在调 compiler-explorer 屎山，发现他们生成 LLVM IR 输出的代码是这么写的：
1. 调用 clang 并传递
2. 在 clang 执行完毕之后直接开读 example.ll 作为 LLVM IR 输出
起初还以为在这两步之间存在某种奇妙逻辑将 example.s 拷贝至 example.ll ，最后发现是依赖了上述的奇妙 clang 行为
1. 调用 clang 并传递
-Xclang -emit-llvm -S -fsyntax-only -o /tmp/example.s /tmp/example.cpp2. 在 clang 执行完毕之后直接开读 example.ll 作为 LLVM IR 输出
起初还以为在这两步之间存在某种奇妙逻辑将 example.s 拷贝至 example.ll ，最后发现是依赖了上述的奇妙 clang 行为
今天发现，执行
将导致 clang 将 LLVM IR 输出写入名为
将导致 clang 将 LLVM IR 输出写入名为
经进一步检查，发现这是因为
clang++ -S -Xclang -emit-llvm -o foo.s foo.cpp将导致 clang 将 LLVM IR 输出写入名为
foo.s 的文件，而执行clang++ -S -fsyntax-only -Xclang -emit-llvm -o foo.s foo.cpp将导致 clang 将 LLVM IR 输出写入名为
foo.ll 的文件经进一步检查，发现这是因为
-fsyntax-only 的存在会导致 clang driver 不再向 clang -cc1 传递 -o 参数，而 -emit-llvm 又需要一个输出文件，因此 clang -cc1 生成了一个默认的输出文件名即 foo.ll