Sign in with Twitter

Username:

Patrick Walton @pcwalton San Francisco, CA

Research engineer at Mozilla

490 Following   9,320 Followers   8,861 Tweets

Joined Twitter 11/9/09


@cnlohr @whitequark Mesa swrast in a VM, Xwayland. @cnlohr @whitequark The problem is that the internal “is GLX initialized?” check is unsynchronized and process-wide… https://t.co/thF4aKhiiL @cnlohr @whitequark No, that’s not true. Your first GLX call from multiple threads will call __glxInitialize unsync… https://t.co/scfwl2b08U @cnlohr @whitequark That isn’t enough. It causes races. @rikarends @chadaustin The other reason for surfman's existence is to let the app choose the GPU on multi-GPU syste… https://t.co/OWTq1ZN7WO @rikarends @chadaustin It's for sharing textures across threads/processes. Support for that is the main reason why… https://t.co/2QpJOA1xIv @rikarends @chadaustin Of course if you aren't using OpenGL there is no need for GLX :) But we have to support WebGL. @rikarends @chadaustin (Also I'm unsure how reliable texture from pixmap is with EGL, especially on NVIDIA. There i… https://t.co/YEMYCKV07j @rikarends @chadaustin GLX works in more environments, like macOS/XQuartz @chadaustin Unfortunately I can't use that solution. There are two original sins: 1. GLX is an *Xlib* standard, no… https://t.co/wImHKJyJ5Z
11/22
2019
(The real answer is: Use a library—like the one I’m about to release :)—to interface with the GPU. Don’t use GLX di… https://t.co/vPOfGFnb9iPSA: GLX is not thread safe, even if you use XLockDisplay()/XUnlockDisplay(). Xlib-XCB does not fix this. First Goo… https://t.co/TeSJPgzt0dThanks to all of the rav1e contributors bringing us up to speed! (and higher quality too, which isn't measured by P… https://t.co/iFKpT3Aubo
Retweeted by Patrick Walton @msully4321 It’s not just compiler authors, though: I’m referring to things like having to write typename, or https://t.co/wcAuBrMa5lIf people had an appreciation for just how much havoc the lexer hack causes in C and C++, there wouldn't be anywher… https://t.co/oyNTy89hHYThat’s on the nose https://t.co/VanwtebD01
11/21
2019
@ciphergoth GLX so noXSetErrorHandler() may be the worst API I have ever seen. Every time I look I find more horrors, from the lack of a… https://t.co/JODSkJe6Pl @slava_pestov @Catfish_Man But don’t forget closing costs. Those are big (3%). And if you sell your house you lose… https://t.co/SWG99w7pOr"Nefarious websites have analyzed other web browser engines and found flaws that have not been disclosed, and explo… https://t.co/nz3QKMFcn1
Retweeted by Patrick Walton @johnregehr Good taste in board games
11/20
2019
@jckarter Or… y’know… vectorsI'm proud work on this! In this version we've added some @rustlang (we'll have more to say about this in the future… https://t.co/7J5cbAMJH3
Retweeted by Patrick Walton @jckarter I mean, sure, if you have an unfathomably large number of hand-drawn small-size bitmap fonts for every po… https://t.co/EfSZoOW4ZLI think in practice this tends to be most noticeable as small text appearing a little fuzzy under trilinear filteri… https://t.co/qDJV8yrBG1Here’s a bound for single-pixel error for a cached image vs. an SVG rendered via analytic AA. If you offset the cac… https://t.co/5MrcbZi7vW @imoldfella However, rendering vector content fast is still helpful, both because of dynamic content and because if… https://t.co/5CaOhuIpvK @imoldfella I think rendering each frame from scratch isn’t tenable for static content. Even if you hit 60 FPS you’… https://t.co/KqJ7uaW15RI’m always second-guessing what problem my work is trying to solve to try to avoid this trap. e.g. I’m currently sk… https://t.co/RIpeNCzRZMI think this trap applies to research, too. It’s way too easy to slip away from “what problem are people trying to… https://t.co/2ceQ8z8IvA
11/19
2019
@zendrawe Performance. It's almost impossible to beat texture filtering in performance, even with a fast vector ras… https://t.co/hyKBsyYry9Finally finished my latest thesis^H^H^H^H^H^H blog post: https://t.co/ExxvItBPTS
Retweeted by Patrick Waltonhttps://t.co/b19bWjMWQU just makes me so sad. First Chrome refused to remove the behavior back when Firefox didn't… https://t.co/1JGy2Ih1gm
Retweeted by Patrick Walton @avibryant It's trilinear filtering, which is linear interpolation between upscaling and downscaling. Helps to avoid abrupt transitions.
11/18
2019
I think you could mathematically compute an error bound even...It's *really* hard to tell the difference between an SVG rendered at a certain size and a raster image of that SVG… https://t.co/sTaFPqcEd1
11/17
2019
@superfunc @yiningkarlli SameWorse, C-style for loops are flexible in ways that don't matter and are inflexible in ways that do. They hardwire t… https://t.co/hear3vfGJ9It’s really weird that people think C-style for loops are less flexible than iterators and therefore easier to read… https://t.co/Sp18llHQLh @x86instructions ARM
11/16
2019
@johnregehr It saves typing :) @johnregehr This makes it more tolerable: ln -s `xcrun --show-sdk-path` /opt/sdkAgreed. https://t.co/k3vdPZhwu8 @__AllanB With respect: This is easy for you to say, but minorities in China under surveillance by their governments may think differently. @_fruchtose As someone who lives in one of these buildings and knows the neighbors, this is a lie, and it's insulti… https://t.co/DWpo4W4HYEHow am I supposed to believe that modern C++ takes memory safety seriously when people don’t even use .at() instead… https://t.co/Q42ZfiD80NAnother weird C++ belief: Modern C++ doesn’t use raw pointers. If that were true, modern C++ can’t use methods, bec… https://t.co/5DdsGHldRNOne of the weirdest C++ beliefs is that changing “Foo *” to “Foo &” and “foo->x” to “foo.x” suddenly makes all memo… https://t.co/IbTrwFx7av @anniefryman @jasoncrawford @Altimor @NeverSassyLaura @msgHankinson It’s pretty funny reading the NIMBYs in the com… https://t.co/Z68HB3ZeA0
11/15
2019
@whitequark @bascule GPUs were a mistake @Gankra_ @isislovecruft (To be fair, I also have a DirectX Ghidra project) @Gankra_ @isislovecruft It’s not just me, huh? @Gankra_ This is somewhat tongue in cheek, but, like, Intel made the move to 256-bit and actually got very little u… https://t.co/0SEx3srRRp @Gankra_ I actually mostly think that 128 bits is enough for anyone. @TedMielczarek Even though it’s not faster anymore, though, GLSL’s vector syntax is really great just for readability. @TedMielczarek Actually, it’s ironic because shader-level vector code typically isn’t any faster than scalar code o… https://t.co/eERFzMh4QW @fu5ha @Lokathor I’d like to plug pathfinder_simd too :) @TedMielczarek It’s because GLSL puts a lot of effort into ergonomics of vector code. The syntactic sugar runs in t… https://t.co/JJKeWSHQLGThere is no defensible reason why SIMD code should be harder to write than scalar code. GLSL has been around since… https://t.co/z93xwhIPhQWhen taking or returning reference counted objects (if not using smart pointers), please document whether your func… https://t.co/PNpv1at1aO @Michael81936098 Because the memory management scheme fundamentally affects how you write the program. If you try t… https://t.co/bODM4Sqqo2 @Gankra_ I think in practice when people talk about Rust strictness they’re 90% referring to lifetimes and the &/&m… https://t.co/TifawEXGTL @Roguelazer Lots of examples of this in the literature, going back to Tofte and Talpin’s ML Kit. That’s classic reg… https://t.co/AHTVL4LJTpMemory safety with no GC (while still allowing dynamic allocation) is really hard. I’m skeptical it’s possible to d… https://t.co/J8rO43m1d5 @marshray You can turn that warning off, though?If your answer to “Rust is too strict during development” is “throw out safety during both development *and* deploy… https://t.co/Kv83dS7VXhIt’s really easy to criticize Rust for being too “strict”. It’s a lot harder to say what specific changes you’d mak… https://t.co/kIrqyng5KRThe most C++ thing is looking at NULL and deciding that what it needs is to be spelled differently. https://t.co/cIOWhdj13E
Retweeted by Patrick Walton @stephentyrone @shafikyaghmour Even using “0” as null isn’t going to go away.
11/14
2019
@Digital_Cold Yes, but not with the APIs that OS vendors provide—you need a layer on top @WatsonLadd GLSL is OpenGL only, but there’s Direct3D, Metal, Vulkan, CUDA, OpenCL, … @weskerfoot (The reasons the OS vendors won't succeed are (1) nobody has enough market share; (2) they don't realiz… https://t.co/NOF9mc5X4V @weskerfoot I don't have high hopes. The big players want to use their APIs to achieve vendor lock-in. They won't s… https://t.co/SNy9nuRfg3 @crzwdjk The problem isn't Khronos... they're doing the right thing. The problem is that the economics encourage in… https://t.co/BU4QEiXgjv
11/13
2019
Credit the Web for forcing the vendors to collaborate on something (WebGPU), even though it's confined to browsers at the moment.I think the situation might be less bad if OS's provided no shader compilers at all. At least then we could just us… https://t.co/HNvg2fAhAQIt's pretty sad that projects like gfx-rs have to spend enormous effort to provide a cross-platform abstraction ove… https://t.co/rY7HEy2pH1 @kookie13 @ProfSchleich @CSElmendorf @carla_org @Yimby_Law Curious: If this is a slam-dunk argument, why is appeal being seen as a risk? @khuey_ It’s gonna be awesome when SB 50 passes only to have it be struck down along with RHNA, the density bonus, SB 330, and the HAAi love how whenever rust stabilizes a subset of a larger feature people usually find a way to hack back the larger… https://t.co/wrWyJ0NyoE
Retweeted by Patrick Walton @whitequark Yeah, but presumably __STDC_VERSION__ allows more than one digit per version number component @paulbaumgart The thing is, OpenGL is on version 4 so I don’t think any more 1.x versions can ever be released!I’m not sure whether this code to check (major < 2 || (major == 2 && minor <= 1)) is clever or extremely cursed https://t.co/PiqbpSj8mERight as I tweet that I realize that this principle would exclude all I/O tests as the Linux kernel has no testsIs it pointless to write unit tests for Rust libraries that wrap libraries that don’t have any tests themselves?Current status: Lies, damn lies, and GLX documentation. https://t.co/7p0uFgQFeV
11/12
2019
@ciphergoth The most important thing is that using the lack of stack probes on ARM as an excuse to write in C is ri… https://t.co/DmJATPDwjB @ciphergoth It's something we would like to implement on ARM. Mostly requires some LLVM work. @ciphergoth And in the very unlikely event that this were exploitable on ARM or whatever (remember, you would have… https://t.co/ehOd6CSb9C @ciphergoth There's always a guard page and at least on most platforms there is a stack probe as well for large act… https://t.co/wSO0wnpuAFCalling a *checked* stack overflow a "buffer overflow" is totally disingenuous. https://t.co/42oJmRObQ3We wrote __probestack for this. https://t.co/MEwBOhBkgA "Could be exploitable?" Come on. https://t.co/1RsLekzUET
11/11
2019
@hsivonen Working on stable Rust is the big one. I also prefer GLSL-style .xyzw syntax to the shuffle macro, though… https://t.co/pLW0kb12Kc @RichFelker Right.pathfinder_simd is a simple 128-bit SIMD abstraction with a scalar fallback. It has implementations for x86-64 and… https://t.co/capeZtv21PJust published a couple of useful Rust libraries that I use for several of my projects: https://t.co/C5zs8xf6lY and… https://t.co/MjLD4XODes @fugueish I’m pretty sure the state is going to take away the BoS’ toys fairly soon so it won’t matter much.
11/10
2019
@yawaramin @jckarter @superfunc That is the most Facebook project I have ever seen @jckarter @superfunc ocaml_of_php @jckarter @Gankra_ I wonder what the perf would be like if you had the ability to generate specialized bytecode at… https://t.co/KPD5h55fdo
11/9
2019

0