|
From: | Flavio Cruz |
Subject: | Re: [PATCH] mig: explicitly use -std=gnu11 |
Date: | Wed, 23 Nov 2022 11:41:43 -0500 |
On Wed, Nov 23, 2022 at 11:51:36AM +0100, Samuel Thibault wrote:
Flavio Cruz, le mer. 23 nov. 2022 00:10:10 -0500, a ecrit:Latest GCC will pick up gnu17 by default but gnu11 will be better supported with older compilers.Mmm, but why explicitly requesting gnu11 then? Latest GCC will be fine with using gnu17, and older GCC will be fine with using whatever it supports.
I would like to modernize some parts of the mig code (for example, use stdbool.h instead of setting up our own boolean type). For this, gnu99 would be enough but I thought gnu11 would be fine since it has been around
for some time.
--- Makefile.am | 1 + 1 file changed, 1 insertion(+) diff --git a/Makefile.am b/Makefile.am index 918efa1..a528b85 100644 --- a/Makefile.am +++ b/Makefile.am @@ -3,6 +3,7 @@ libexec_PROGRAMS = migcom bin_SCRIPTS = mig +AM_CFLAGS = -std=gnu11 AM_YFLAGS = -d EXTRA_DIST = gensym.awk cpu.sym -- 2.37.2
[Prev in Thread] | Current Thread | [Next in Thread] |