From: "\"徐林" <francisco_flynn@foxmail.com>
To: =?gb18030?B?TGVpZiBMaW5kaG9sbQ==?= <leif.lindholm@linaro.org>,
=?gb18030?B?ZGV2ZWw=?= <devel@edk2.groups.io>,
=?gb18030?B?cGV0ZQ==?= <pete@akeo.ie>
Subject: Re: [edk2-devel] tool chain tag setting for vs2017
Date: Wed, 8 May 2019 23:48:35 +0800 [thread overview]
Message-ID: <tencent_962028908B2271B4150B234FCDDD94DFE405@qq.com> (raw)
In-Reply-To: <20190508145400.7gvhxqhzawije75s@bivouac.eciton.net>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 2257 bytes --]
>
>On Wed, May 08, 2019 at 03:44:45PM +0100, Pete Batard wrote:
>> On 2019.05.08 13:16, xulin wrote:
>> > Got it. BTW, do you have plan to support for higher version GCC? Such as
>> > GCC8?
>>
>> Well, I am not speaking for the project as a whole, but past experience
>> seems to indicate that support for newer toolchain is added by contributors
>> (which, really, can be anyone) on an ad hoc basis, when the need is
>> identified and/or a new toolchain becomes popular, as well as *if* the
>> definitions from the current toolchain (such as GCC5) do not work well
>> enough to support the later versions.
>>
Certainly.
GCC5 is working good on Ubuntu 16.04, but i have another PC with Ubuntu 18.10
installed, and i can't just install gcc-5 with apt-get install, i guess gcc-5
package is removed from apt source, i believe i can find a way to install
gcc-5 on Ubuntu 18.10 with some effort... but i would not try to, because
VS2017 works good now :)
>> So I don't think there are official plans with regards to adding such an
>> such toolchain (such as GCC8 or VS2019) apart from waiting for contributors,
>> who might have a vested interest in those, to provide patches where needed.
>> For most Open Source projects, this usually happen organically, without any
>> specific timeline, as each toolchain becomes more widespread.
>
>Correct.
>
>Basically, GCC 4.x was an absolute mess in changing command line
>options and behaviours (cetainly on the ARM* side, but I think also
>for x86). Since GCC 5.0, this has stabilised a lot, so we
>haven't needed to produce any version-specific profiles since that one.
>
>GCC9 looks "interesting" in throwing up new buildtime warnings (from
>looking at other projects), so it might be that it will need a new
>profile, but it may also be that all those are genuine bugs and need
>to be fixed.
Oh..I didn't notice that GCC9 is available now, maybe i should check the
release News.
Thank you :)
Regards,
Flynn
>
>Certainly, any issues people come across, please report.
>
>Regards,
>
>Leif
[-- Attachment #2: Type: text/html, Size: 5147 bytes --]
next prev parent reply other threads:[~2019-05-08 15:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 8:00 tool chain tag setting for vs2017 "徐林
2019-05-08 10:25 ` [edk2-devel] " Pete Batard
2019-05-08 12:16 ` "徐林
2019-05-08 14:44 ` Pete Batard
2019-05-08 14:54 ` Leif Lindholm
2019-05-08 15:48 ` "徐林 [this message]
2019-05-09 0:29 ` Liming Gao
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=tencent_962028908B2271B4150B234FCDDD94DFE405@qq.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