From 287473027e9f72a624a532254864c07b737c0152 Mon Sep 17 00:00:00 2001 From: Ekaitz Zarraga Date: Tue, 8 Jun 2021 16:56:59 +0200 Subject: Update lightening with some rewording --- content/lightening.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'content') diff --git a/content/lightening.md b/content/lightening.md index d754082..9344aa5 100644 --- a/content/lightening.md +++ b/content/lightening.md @@ -1,11 +1,11 @@ -Title: RISC-V Adventures: Migrating Lightening +Title: RISC-V Adventures: Lightening Date: 2021-05-19 Category: Tags: Slug: lightening Lang: en Summary: - The Migration of Lightening, the code generation library used in + The port of Lightening, the code generation library used in Guile Scheme, and other adventures on the low level world of RISC-V. In [the latest post](https://ekaitz.elenq.tech/2020.html) I summarized the last @@ -26,8 +26,8 @@ RISC-V. From that, and I don't really know how, I started taking part on the efforts of -migrating Guix to RISC-V. One of the things I'm working on right now is the -migration of the machine code generation library that Guile uses, called +porting Guix to RISC-V. One of the things I'm working on right now is the +port of the machine code generation library that Guile uses, called `lightening`, to RISC-V, and that's what I'm talking about today. @@ -59,7 +59,7 @@ Boom! Lightened! ### The process So Lightening is basically simpler but the idea is the same. But how do you -make the migration of a library like that to other architecture? +make the port of a library like that to other architecture? The idea is kind of simple, but we need to talk about the basics first. -- cgit v1.2.3