From: "Ard Biesheuvel" <ard.biesheuvel@arm.com>
To: Laszlo Ersek <lersek@redhat.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 20:14:13 +0300 [thread overview]
Message-ID: <dd153426-1fc5-60ce-dced-449937076dca@arm.com> (raw)
In-Reply-To: <d974c756-9863-62f4-c153-4e4a2e39de73@redhat.com>
On 8/31/20 6:27 PM, Laszlo Ersek wrote:
> On 08/31/20 18:18, Laszlo Ersek wrote:
>
>> Obviously the following form would be preferred:
>>
>> scl enable example -- less --version
>>
>> Because this form would not require quoting, just prefixing.
>
> I need to slow down when reading manual pages. Now that I've actually
> *tried* the above, it works! And upon re-reading the manual, it's even
> *documented*; just not in the examples section.
>
> Where's my brown paper bag again...
>
:-)
Happy to hear that you managed, and that you are on board with
deprecating GCC48.
Given our successful efforts to make the GCC5 profile work with all GCC
versions since the 5.x series, I think we should consider dropping GCC48
*and* GCC49, as well as CLANG35 (which only supports ARM anyway, and is
superseded by CLANG38 which should also support any Clang version
released since)
To Liming's point, renaming the profiles may have additional impact
which we are not prepared to deal with, so that could be a separate
matter. But removing GCC48, GCC49 and CLANG35 reduces the CI effort, and
allows us to focus our support on profiles that are actually in wide use.
prev parent reply other threads:[~2020-08-31 17:14 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
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 [this message]
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=dd153426-1fc5-60ce-dced-449937076dca@arm.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