~garritfra

https://garrit.xyz

I write bugs for a living. Linux and other cool stuff in my spare time.

~garritfra/antimony

Last active 1 year, 6 months ago

~garritfra/flutterflux

Last active 1 year, 7 months ago

~garritfra/midgard

Last active 1 year, 8 months ago

~garritfra/taurus

Last active 1 year, 9 months ago

~garritfra/omega

Last active 1 year, 10 months ago

~garritfra/public-inbox

Last active 1 year, 10 months ago

~garritfra/notiz

Last active 2 years ago

~garritfra/express-rs

Last active 2 years ago

~garritfra/wireguard-tools-announce

Last active 2 years ago

~garritfra/wireguard-tools-discuss

Last active 2 years ago
View more

Recent activity

Brew Package 3 months ago

From Garrit Franke to ~mpu/qbe

Congrats on the recent release!!

Just a quick announcement that QBE is now available through the Brew 
package manager:

https://formulae.brew.sh/formula/qbe

Cheers
Garrit

Re: [PATCH] Add snapcraft packaging 5 months ago

From Garrit Franke to ~mpu/qbe

On 03.05.22 16:47, Zygmunt Krynicki wrote:
> I was interested in Hare so I started looking at dependencies and found
> QBE. The snapcraft packaging is straightforward, with core20 base,
> makefile-base part, one application and minimal meta-data. I've chose to
> use git-based versions, which is convenient when having automatic builds
> published to the snap store. The qbe application uses the home plug for
> convenience.

I was thinking about maintaining a Brew formula for QBE once it hits 
1.0, which I think is a similar undertaking as this snap package.

I don't think this should be part of QBE itself, neither do I think we 
should provide automatic publishing, but I'd propose to move it to 
`contrib/snap/`, implying that it's not *officially* maintained by the

[PATCH v6] cli: add -v flag 6 months ago

From Garrit Franke to ~mpu/qbe

---
Sorry about the spam. I still have a long way to go when it comes to
email patches. It won't happen again!

 Makefile | 4 +++-
 main.c   | 6 +++++-
 2 files changed, 8 insertions(+), 2 deletions(-)

diff --git a/Makefile b/Makefile
index 711873b..3232a9b 100644
--- a/Makefile
+++ b/Makefile
@@ -1,4 +1,5 @@
BIN = qbe
[message trimmed]

[PATCH v5] cli: add -v flag 6 months ago

From Garrit Franke to ~mpu/qbe

>>  		case 'v':
>>  			hf = c != 'v' ? stderr : stdout;
>> -			fprintf(hf, "%s\n", QbeVersion);
>> +			fprintf(hf, "%s\n", QBE_VERSION);
>>  			exit(c != 'v');

> What's the point of this logic?
> Why not puts(Version); exit(0);

I guess that's just me sucking at C. :)

v5: Move VER variable up; simplify version emit
---
 Makefile | 4 +++-
[message trimmed]

[PATCH v4] cli: add -v flag 6 months ago

From Garrit Franke to ~mpu/qbe

Since we're approaching v1.0, I thought it would be helpful to be able
to view the version of the built binary. At compile-time, the contents
of the VERSION file are thrown in the `QbeVersion` macro.

This approach seemed the most reasonable to me, but I'm open for
suggestions.

v2: simplify version source
v3: fix screwup
v4: use lowercase define
---
 Makefile | 4 +++-
 main.c   | 8 +++++++-
 2 files changed, 10 insertions(+), 2 deletions(-)
[message trimmed]

[PATCH] config: uppercase defines 6 months ago

From Garrit Franke to ~mpu/qbe

I don't know if there's a reason for the config defines to be in upper
camel case notation, but using screaming snake case seems more
appropriate.

---
 Makefile | 12 ++++++------
 main.c   |  4 ++--
 2 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/Makefile b/Makefile
index 711873b..7f07e17 100644
--- a/Makefile
+++ b/Makefile
@@ -41,20 +41,20 @@ $(OBJDIR)/main.o: config.h
[message trimmed]

[PATCH v3] cli: add -v flag 6 months ago

From Garrit Franke to ~mpu/qbe

Whoops, forgot to drop v1.

---
 Makefile | 4 +++-
 main.c   | 8 +++++++-
 2 files changed, 10 insertions(+), 2 deletions(-)

diff --git a/Makefile b/Makefile
index 711873b..eebbb05 100644
--- a/Makefile
+++ b/Makefile
@@ -14,6 +14,7 @@ AMD64OBJ = $(AMD64SRC:%.c=$(OBJDIR)/%.o)
ARM64OBJ = $(ARM64SRC:%.c=$(OBJDIR)/%.o)
RV64OBJ  = $(RV64SRC:%.c=$(OBJDIR)/%.o)
[message trimmed]

[PATCH v2] cli: add -v flag 6 months ago

From Garrit Franke to ~mpu/qbe

> -1 to shelling out, why not just put it in the Makefile directly? 

Fair. I looked at how the TCC project did this, but I suppose putting
the version in the Makefile is less overhead.

> And the macro should be uppercase, VERSION or QBE_VERSION.

It irritated me that the other config defines (Defasm and Deftgt) are
not using that format. Worth another patch?

---
 Makefile | 4 ++--
 VERSION  | 1 -
 main.c   | 2 +-
[message trimmed]

[PATCH] cli: add -v flag 6 months ago

From Garrit Franke to ~mpu/qbe

Since we're approaching v1.0, I thought it would be helpful to be able
to view the version of the built binary. At compile-time, the contents
of the VERSION file are thrown in the `QbeVersion` macro.

This approach seemed the most reasonable to me, but I'm open for
suggestions.

---
 Makefile | 4 +++-
 VERSION  | 1 +
 main.c   | 8 +++++++-
 3 files changed, 11 insertions(+), 2 deletions(-)
 create mode 100644 VERSION
[message trimmed]

QBE IR for Rust 7 months ago

From Garrit Franke to ~mpu/qbe

Hi,

I just published an initial version of a QBE IR library for Rust. Alexey Yerin
originally developed this for Antimony [0], but other projects using QBE as
a backend could benefit from this as well. Here's a link to the project:

https://github.com/garritfra/qbe-rs

Thanks,
Garrit

[0]: https://github.com/antimony-lang/antimony/blob/master/src/generator/qbe.rs