emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#40009: closed ([core-updates PATCH]: Use per-architecture GCC for li


From: GNU bug Tracking System
Subject: bug#40009: closed ([core-updates PATCH]: Use per-architecture GCC for libstdc++-boot0)
Date: Wed, 11 Mar 2020 06:53:02 +0000

Your message dated Wed, 11 Mar 2020 08:51:32 +0200
with message-id <20200311065132.GC26542@E5400>
and subject line Re: [bug#40009] [core-updates PATCH]: Use per-architecture GCC 
for libstdc++-boot0
has caused the debbugs.gnu.org bug report #40009,
regarding [core-updates PATCH]: Use per-architecture GCC for libstdc++-boot0
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden.)


-- 
40009: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=40009
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: [core-updates PATCH]: Use per-architecture GCC for libstdc++-boot0 Date: Tue, 10 Mar 2020 13:12:27 +0200
I've tested this on aarch64 and there were no problems. It also
provides a nice framework for other architectures as they become
supported.


-- 
Efraim Flashner   <address@hidden>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

Attachment: 0001-gnu-libstdc-boot0-Use-per-architecture-gcc-versions.patch
Description: Text document

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- Subject: Re: [bug#40009] [core-updates PATCH]: Use per-architecture GCC for libstdc++-boot0 Date: Wed, 11 Mar 2020 08:51:32 +0200
On Tue, Mar 10, 2020 at 08:21:08PM +0100, Marius Bakke wrote:
> Efraim Flashner <address@hidden> writes:
> 
> > I've tested this on aarch64 and there were no problems. It also
> > provides a nice framework for other architectures as they become
> > supported.
> 
> What is the benefit of this patch?  I'd prefer to keep libstdc++-boot0
> identical across architectures for simplicity, unless there is a good
> reason to do otherwise (say, porting to a new architecture).
> 
> Now we could end up in a situation where someone patches GCC5 on
> 'master' and accidentally triggers a full rebuild on AArch64.

Sound reasoning. And currently most of the porting work makes use of
GCC7 and not GCC5. I'm closing this bug.


-- 
Efraim Flashner   <address@hidden>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

Attachment: signature.asc
Description: PGP signature


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]