From: Robbie Harwood <rharwood@redhat.com>
To: development@efficientek.com, Daniel Kiper <dkiper@net-space.pl>
Cc: grub-devel@gnu.org
Subject: Re: Minimum compiler version (was: Re: [PATCH v5 0/4] Update gnulib and drop some patches)
Date: Mon, 28 Feb 2022 12:24:50 -0500 [thread overview]
Message-ID: <jlgh78ilx99.fsf@redhat.com> (raw)
In-Reply-To: <20220225195046.62895cec@crass-HP-ZBook-15-G2>
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
Glenn Washburn <development@efficientek.com> writes:
> GCC 5.1.0 looks like it came out on April 22, 2015[1] and 5.2 was used
> in Ubuntu Xenial from 2016 (which is no longer supported). At what
> point do we bump up the minimum supported version? And doing so
> wouldn't mean that GRUB can't be compiled with eariler versions of
> GCC, it just means we don't test that. I also think it would be
> acceptable to accept patches that fix issues with compiling on GCC
> versions less than the stated minimum supported version (with in
> reason and subject to discretion).
>
> One idea is to update the minimum supported version every release cycle
> to the lowest GCC version that is about 5 years old (that's artitrary
> but seems reasonable).
>
> I'm interested in this because it seems to imply that for the testing
> system it should do two compilations for every target, one for the
> munimum supported GCC and one for a somewhat recent version.
I support raising the minimum compiler version.
Looking at https://www.gnu.org/software/gcc/releases.html , a five-year
proposal would raise to gcc-7.
Be well,
--Robbie
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2022-02-28 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 1:50 Minimum compiler version (was: Re: [PATCH v5 0/4] Update gnulib and drop some patches) Glenn Washburn
2022-02-26 7:37 ` Heinrich Schuchardt
2022-02-28 17:24 ` Robbie Harwood [this message]
2022-03-04 20:25 ` Daniel Kiper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jlgh78ilx99.fsf@redhat.com \
--to=rharwood@redhat.com \
--cc=development@efficientek.com \
--cc=dkiper@net-space.pl \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.