From: "Laszlo Ersek" <lersek@redhat.com>
To: Ard Biesheuvel <ard.biesheuvel@arm.com>,
Leif Lindholm <leif@nuviainc.com>
Cc: Pierre Gondois <Pierre.Gondois@arm.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"bob.c.feng@intel.com" <bob.c.feng@intel.com>,
"liming.gao@intel.com" <liming.gao@intel.com>,
Tomas Pilar <Tomas.Pilar@arm.com>, nd <nd@arm.com>
Subject: Re: [edk2-devel] [PATCH V2 2/2] BaseTools: Factorize GCC flags
Date: Mon, 31 Aug 2020 16:03:43 +0200 [thread overview]
Message-ID: <ea1e8e5f-5b02-99bc-c2c6-3f130db1ac46@redhat.com> (raw)
In-Reply-To: <f1aae5a9-b788-a06c-a46b-c534e92b1b89@arm.com>
On 08/31/20 15:22, Ard Biesheuvel wrote:
> mainline EDK2 is arguably a development tree
I agree.
> not a stable production tree for ~5 year old firmware builds
I agree with that too.
But I don't think GCC48 is "holding back" edk2. I don't know of a
firmware feature that suffers because I'd like to be able to build the
tree with GCC48.
(LTO is not a firmware feature; and NOOPT builds, which are important,
don't / shouldn't enable LTO anyway.)
I do agree that maintaining the BaseTools stuff that's related to GCC48
is a burden, technically speaking. Is it a big burden? Should I attempt
to handle related issues?
Official Software Collections / Developer Toolset add-ons exist for
RHEL7:
https://developers.redhat.com/products/developertoolset/overview
https://access.redhat.com/documentation/en-us/red_hat_developer_toolset/9/html/user_guide/chap-red_hat_developer_toolset#sect-Red_Hat_Developer_Toolset-Compatibility
I've played with them in the past. They weren't a good fit for me, as I
recall. Anyway, I can check them out again, if I must.
> and so I do think we should get rid of GCC48 even before RHEL7 goes
> EOL.
We might want to explore the Debian / Ubuntu status too (LTS).
Thanks,
Laszlo
next prev parent reply other threads:[~2020-08-31 14:03 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 8:35 [PATCH V2 0/2] Add gcc flag for void* pointer arithmetics PierreGondois
2020-07-07 8:35 ` [PATCH V2 1/2] BaseTools: Add gcc flag to warn on void* pointer arithmetic PierreGondois
2020-07-16 9:07 ` [edk2-devel] " Yuwei Chen
2020-07-20 4:10 ` Bob Feng
2020-07-22 18:05 ` [edk2-devel] " Leif Lindholm
2020-07-22 21:13 ` Andrew Fish
2020-07-23 1:56 ` Bob Feng
2020-07-23 2:49 ` Andrew Fish
2020-07-23 9:33 ` Leif Lindholm
2020-07-24 3:56 ` Bob Feng
2020-07-24 9:01 ` PierreGondois
2020-07-24 11:05 ` Leif Lindholm
2020-07-24 11:03 ` Leif Lindholm
2020-07-07 8:35 ` [PATCH V2 2/2] BaseTools: Factorize GCC flags PierreGondois
2020-07-20 4:11 ` Bob Feng
2020-07-30 12:08 ` [edk2-devel] " Leif Lindholm
2020-07-22 11:03 ` Laszlo Ersek
2020-07-22 11:24 ` Laszlo Ersek
2020-08-26 16:42 ` Laszlo Ersek
2020-08-27 8:32 ` PierreGondois
2020-08-27 14:55 ` Laszlo Ersek
2020-08-27 15:25 ` Leif Lindholm
2020-08-28 16:56 ` Laszlo Ersek
2020-08-28 19:15 ` Leif Lindholm
2020-08-31 13:22 ` Ard Biesheuvel
2020-08-31 13:43 ` 回复: " gaoliming
2020-08-31 14:03 ` Laszlo Ersek [this message]
2020-08-31 14:37 ` Ard Biesheuvel
2020-08-31 16:18 ` Laszlo Ersek
2020-08-31 16:27 ` Laszlo Ersek
2020-08-31 17:14 ` Ard Biesheuvel
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-list 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=ea1e8e5f-5b02-99bc-c2c6-3f130db1ac46@redhat.com \
--to=devel@edk2.groups.io \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox