From: "Leif Lindholm" <leif@nuviainc.com>
To: Laszlo Ersek <lersek@redhat.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>,
Ard Biesheuvel <Ard.Biesheuvel@arm.com>
Subject: Re: [edk2-devel] [PATCH V2 2/2] BaseTools: Factorize GCC flags
Date: Fri, 28 Aug 2020 20:15:15 +0100 [thread overview]
Message-ID: <20200828191515.GC1191@vanye> (raw)
In-Reply-To: <42cb48da-b932-7006-475b-d5259bcd0d8a@redhat.com>
On Fri, Aug 28, 2020 at 18:56:45 +0200, Laszlo Ersek wrote:
> >> Leif, please comment!
> >
> > I did propose reverting it. But I asked for Ard's feedback on the
> > reason for why we had the break in the flags-chain, in case he
> > remembered (and he was on holiday at the time).
> >
> > Basically, I'm wondering whether we're better off changing this
> > behaviour or simply nuking GCC48.
>
> I use GCC48 daily -- it's the system compiler on RHEL7. My laptop runs
> RHEL7 -- I value stability above all.
That explains why it's still in then :)
OK, so then cleaning it up would be nice.
/
Leif
next prev parent reply other threads:[~2020-08-28 19:15 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 [this message]
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
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=20200828191515.GC1191@vanye \
--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