Date: Mon, 07 Dec 2020 18:09:36 +0000 From: bugzilla-noreply@freebsd.org To: powerpc@FreeBSD.org Subject: [Bug 251670] lang/gcc10: add support for powerpc64le Message-ID: <bug-251670-25139-DzZ68PMtv4@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-251670-25139@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251670 Gerald Pfeifer <gerald@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open Flags|maintainer-feedback?(gerald |maintainer-feedback- |@FreeBSD.org) | CC| |andreast@FreeBSD.org --- Comment #2 from Gerald Pfeifer <gerald@FreeBSD.org> --- Piotr, thanks for submitting this upstream, too! I'm ust afraid you missed Andreas T. both there and here, so let me include him on this PR. Andreas is FreeBSD src committer and upstream maintainer for FreeBSD in GCC, so can approve most of your changes. The sequence of events how it usually should go: 1. Upstream HEAD (that will become GCC 11) 2. lang/gcc11-devel picks that up within days 3. Backport to upstream GCC 10 branch 4. lang/gcc10-devel picks that up within days 5. Backport to lang/gcc10 6. Obsolete local patches as the next GCC 10 release comes out (Steps 2 and 3 can take place in parallel.) Let's try not to skip too many of the steps 2-4 (or 1-4). ;-) It really is the safer, future proof, and in the end easier way. -- You are receiving this mail because: You are on the CC list for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-251670-25139-DzZ68PMtv4>