summaryrefslogtreecommitdiff
path: root/content
diff options
context:
space:
mode:
authorEkaitz Zarraga <ekaitz@elenq.tech>2021-06-08 16:56:59 +0200
committerEkaitz Zarraga <ekaitz@elenq.tech>2021-06-08 16:56:59 +0200
commit287473027e9f72a624a532254864c07b737c0152 (patch)
tree40b6f849317ffe5a375140d5ab6216ad8b2e37fb /content
parentb42d02dee5a9bf410120e0eda00dc5deae4426aa (diff)
Update lightening with some rewording
Diffstat (limited to 'content')
-rw-r--r--content/lightening.md10
1 files changed, 5 insertions, 5 deletions
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.
<http://www.riscvbook.com/>
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.