janriemer, to rust

How to speed up #Rust compile times by 16x 🚀

In their blog post "Speeding up Rust edit-build-run cycle" David Lattimore shows how you can speed up #RustLang compile times by 16x by just changing some default compiler config:

https://davidlattimore.github.io/working-on-rust-iteration-time.html

Excellent read! Highly recommend!

Make sure to read to the end, as there is a surprise awaiting you - it's pretty wild.

#Compiler #Performance #wild

janriemer, (edited ) to javascript

This is mad 🤯

oxc - The Oxidation #Compiler is creating a suite of high-#performance tools for the #JavaScript / #TypeScript language re-written in #Rust - by Boshen:

https://github.com/web-infra-dev/oxc

Its linter is 50 - 100 times faster than #ESLint...

https://github.com/Boshen/bench-javascript-linter

...and its parser is even 2x faster than #swc

https://github.com/Boshen/bench-javascript-parser-written-in-rust

#JS tooling goes brrrrrrrrrrr! 🚀

#RustLang #WebDev #WebDevelopment

gabrielesvelto, (edited ) to random
@gabrielesvelto@fosstodon.org avatar

Friends from the and community, I have a question about Python's copy-and-patch JIT. This article claims it's a novel technique introduced in 2021: https://tonybaloney.github.io/posts/python-gets-a-jit.html

However this looks awfully like inline-threading which was first presented in 1998 (see this: https://dl.acm.org/doi/pdf/10.1145/277650.277743) and has already been applied to other languages and VMs (see for example SableVM's 2003 paper about their implementation: https://www.sable.mcgill.ca/publications/papers/2003-2/sable-paper-2003-2.pdf).

Is it really a different approach?

deadblackclover, to badminton
@deadblackclover@functional.cafe avatar

A book about compiling Racket and Python to x86-64 assembly

https://github.com/IUCompilerCourse/Essentials-of-Compilation

shakthimaan, to random
@shakthimaan@mastodon.social avatar
minioctt, to Sony Italian

Altri di , ma in questo caso non colpa di : avevo visto (con rabbia e disperazione) che i Nestopia-UE e per (e questo punto chissà quanti altri!) facevano piantare per qualche secondo la , che poi si spegneva con un pop. A questo punto decido di vedere se anche su … e si, succede la stessa cosa, quindi non è colpa del mio hardware. 🤯️

Il grazioso mi dice però precisamente il motivo del … un jump a NULL, che è una cosa non proprio bella (in alto in foto), e mi dice molto poco. Purtroppo sulla PSP mi serve uno di quei core, perché voglio tenere quanta più possibile della mia centralizzata in RetroArch, e a quanto pare FCEUmm (l’unico altro disponibile per il ) ha qualche problema: inizialmente funzionava (come in basso a sinistra in foto), ma poi ha iniziato a rompere il video in modo (in basso a destra). (No, non ho provato a resettare tutta la configurazione, perché anche se risolvesse ora il non potrei farlo ogni volta che si ripresenta.) 💀️

https://octospacc.altervista.org/wp-content/uploads/2024/02/image-4-960x524.pngPurtroppo, come ormai sempre più mi capita, non trovo alcuna informazione rilevante al problema cercando sul web. E allora, unica mia possibilità: mi metto con l’animo in pace e provo a ritroso tutte le di RetroArch per la piattaforma, fino a trovare il punto di dove quei 2 core si sono rotti: a quanto pare, tra il 20 gennaio 2022 e il 5 marzo 2022; la 1.10.0 è a posto (stando a PPSSPP, ancora non ho provato sul vero metallo), mentre già la 1.10.1 presenta la . E noto una singola e particolare : il passaggio della del da 9.3.0 a 11.2.0. 🧐️

https://octospacc.altervista.org/wp-content/uploads/2024/02/image-5-960x275.png…A chi devo dare la colpa ora? Saranno stati quelli di GNU ad aver roba upstream? O piuttosto quelli dell’SDK per ? Perché ho skimmato commit e release della roba di , ma non riesco ad individuare il problema lì. Ma in ogni caso, perché certi core hanno smesso di funzionare brutalmente ed altri no? Questi sono i motivi per cui odio il . Ora non so nemmeno a chi devo creare la a riguardo. 🗡️

Per ora, la mia unica è di usare questa versione vecchietta del , sperando che non ci siano incompatibilità di savestate tra versioni diverse, perché voglio giustamente tenere quelle aggiornate sui dispositivi dove funzionano. Avendo poi più tempo, potrei tentare di compilare una versione recente del pacchetto usando il vecchio… ma probabilmente non ci riuscirò. 😩️

https://octospacc.altervista.org/2024/02/04/pspspsp-non-gradisce-nuovo-gcc/

DOSBox_Staging, to opensource
@DOSBox_Staging@corteximplant.com avatar

Unrelated pic of the day: DOSBox Staging compiler warnings (2019-2020)

#dosbox #dosgaming #msdos #emulation #retrogaming #linuxgaming #macgaming #foss #codequality #compiler #qualitycode

cpponline, to cpp

What’s New in Compiler Explorer? 2024 Update – by @mattgodbolt – C++Online 2024

https://www.youtube.com/watch?v=28Gp3TTQYp0

#compiler #compilerexplorer #cpp #programming

deadblackclover, to rust
@deadblackclover@functional.cafe avatar
UweHalfHand, to scheme

#wile #scheme #compiler version (0 9 2) is out at https://github.com/uhollerbach/wile
See changelog for details, big thing this time was implementing an interpreter which is now going to get glued into compiler, to provide the ability to deal with macros — user-defined code which runs at compile time.

jesper, to haskell

This is a great blog post on the WellTyped blog on specialization in Haskell! It's a good reminder that I (or someone) should really get around to getting rid of -fexpose-all-unfoldings and -fspecialize-agressively in the Agda codebase.

well-typed.com/blog/2024/04/choreographing-specialization-pt1/

(Also I didn't know about -flate-specialise and -fpolymorphic-specialisation, though I think I'd rather avoid relying on even more flags.)

#Haskell #compiler #performance #blog

avp, to scheme
0xor0ne, to infosec

Nice free course by Cornell university for learning a couple of things about compilers and programming languages implementations

https://cs.cornell.edu/courses/cs6120/2020fa/self-guided/

Github repo: https://github.com/sampsyo/cs6120

#infosec #cybersecurity #compiler

image/jpeg
image/jpeg

meisterluk, to webassembly

"The challenge of cross-language interoperability" by David Chisnall (2013)
https://dl.acm.org/doi/10.1145/2534706.2534719

The author is craving for an intermediate representation for general-purpose computational machines. A few years later it happened with #WebAssembly. #computerScience #compiler

shakthimaan, to random
@shakthimaan@mastodon.social avatar

Grace is an OCaml library with interfaces to build, report and render beautiful compiler error messages https://github.com/johnyob/grace #OCaml #Compiler #Usability

shakthimaan, to javascript
@shakthimaan@mastodon.social avatar

Improving the dead code elimination algorithm in js_of_ocaml https://www.micahcantor.com/blog/js-of-ocaml-dead-code/ #JavaScript #OCaml #Compiler @tarides_

janriemer, to showerthoughts

Feature request for code editors:

Command for jumping to the next file that has #compiler errors.

#Code #CodeEditor #Idea #Feature #Editor #LSP

janriemer, to ai

Inventing software that can "understand" context-dependent, ambiguous natural language, so that we can let it generate software with a context-free, unambiguous language. ➰

What can go wrong!? :awesome:

#AI #ArtificialIntelligence #ChatGPT #LLM #SALAMI #ContextFree #ProgrammingLanguage #Compiler

8bitboyz, to random

This looks like an API I just might have to try out!!

RT @SyntaxErrorSoft
My Pascal 6502 compiler to try :) #Pascal #compiler #6502 #8BitCoders
https://syntaxerrorsoftware.itch.io/pas6502
https://twitter.com/SyntaxErrorSoft/status/1649256342069325824

UweHalfHand, to scheme

Hey all, for those of you who are scheme aficionados, I have been working on a small scheme compiler, and it is starting to be halfway decent, in my admittedly biased opinion. I have just shoved the first public release of it onto github, at https://github.com/uhollerbach/wile — it is named after that great super-genius schemer, Wile E Coyote 😊

If you are interested in this sort of stuff, I would appreciate feedback.

#scheme #compiler

f4grx, to random French
@f4grx@chaos.social avatar

friends, my B #compiler is starting to generate cool stuff.

However it is hard to find real B source code.

Can you please generate some test B programs to torture test my compiler?

You can compile it with a simple linux 'make' command:

https://git.sr.ht/~f4grx/bpars

thanks!

totori, to random

whoopsie. i joined Fedi a few months ago then
(1) got a job
(2) developed an overbearing paranoia about online privacy and stuff
(3) embarked on a WAY overcomplicated journey to back up and synchronise my digital life
and as a consequence felt i didn't have time to "maintain" an "online presence" :wshum:

but i'm back now (with a fresh username)! i kinda take everything too seriously - it's just fun to see what everyone's up to :gphn_happy:

totori,

heya! i'm Tori and i take everything way too seriously, so let's get this outta the way.

i'm a late-blooming computer person, doing #GameEngine #GameDev and also wanting to try more #Compiler stuff - there's so much to learn and it's all so EXCITING, ugh!

some media to get to know me:

  • A Short Hike, Celeste, Mega Man and all things #Nintendo
  • digital fusion, chiptune, spicy math rock, jungle, lofi and everything inbetween (#Bandcamp user!)
  • Studio Ghibli, the Patlabor movies, Gatchaman Crowds

i love #IndieGame(s) and music by small creators and open source and stuff! hope spending time here will put more cool works on my radar.

#Introduction

bread80, to random
@bread80@mstdn.social avatar

I've renamed the EXTERN directive to CALL. That feels a lot more logical given it's function (to call assembly code such as ROM routines).

It also makes it straightforward to implement an RST directive to call assembly via a Z80 RST instruction.

(In the screenshot I've cleaned up the comments in the output to make it easier to read.)

#Quiche #compiler #Z80 #Delphi

bread80, to random
@bread80@mstdn.social avatar

update: Write and writeln marks the end of the the refactoring of operations and primitives which has taken up the last few months.

I've also refactored a few other parts to better future proof them.

There a still a few rough edges to smooth off in the expression parser (implicit types) and code generator (parameter loading and validation).

But this means I can now return to interesting stuff :) as well as moving towards some kind of initial (pre-beta) release.

Output if the test program running on an Amstrad CPC emulator.

boilingsteam, to linux
@boilingsteam@mastodon.cloud avatar
  • All
  • Subscribed
  • Moderated
  • Favorites
  • JUstTest
  • mdbf
  • ngwrru68w68
  • modclub
  • magazineikmin
  • thenastyranch
  • rosin
  • khanakhh
  • InstantRegret
  • Youngstown
  • slotface
  • Durango
  • kavyap
  • DreamBathrooms
  • megavids
  • GTA5RPClips
  • tacticalgear
  • normalnudes
  • tester
  • osvaldo12
  • everett
  • cubers
  • ethstaker
  • anitta
  • provamag3
  • Leos
  • cisconetworking
  • lostlight
  • All magazines