Webinar "A Compiler's View of the OpenMP API" (Johannes Doerfert)

Hi! A webinar has been announced: "A Compiler's View of the OpenMP API" (Johannes Doerfert), ,

gcc-9-20210603 is now available

Snapshot gcc-9-20210603 is now available on https://gcc.gnu.org/pub/gcc/snapshots/9-20210603/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 9 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch

Update to GCC copyright assignment policy

> Sent: Friday, June 04, 2021 at 4:50 AM > From: "Daniel Pono Takamori" > To: gcc@gcc.gnu.org > Subject: Re: Update to GCC copyright assignment policy > > I'm joining this list just briefly to give some feedback and input on this > thread on behalf of Software Freedom Conservancy, since we were

Re: GCC documentation: porting to Sphinx

On Thu, 3 Jun 2021, Martin Liška wrote: > On 6/2/21 6:44 PM, Joseph Myers wrote: > > On Wed, 2 Jun 2021, Joel Sherrill wrote: > > > > > For RTEMS, we switched from texinfo to Sphinx and the dependency > > > on Python3 for Sphinx has caused a bit of hassle. Is this going to be > > > an issue for G

Re: Update to GCC copyright assignment policy

Hi Daniel, On Thu, 3 Jun 2021 12:50:44 -0400 Daniel Pono Takamori wrote: > We definitely don't want to see the GCC mailing list derailed into > discussing this possibly off-topic issue. To be fair, THIS is the correct mailing list to discuss these topics, so much that such major policy change sh

Re: Mailing list reconfiguration: VERP Sender: header affected

On 6/3/21 5:10 PM, D. Hugh Redelmeier wrote: | From: Martin Liška | Which we recommend in the ection Filtering here: | https://gcc.gnu.org/lists.html Thanks for the useful information. That document suggests: * ^List-Id: .*<.*.gcc.gnu.org>$ Surely this should be: * ^List-Id: .*<.*.gcc\.g

Re: Update to GCC copyright assignment policy

I'm joining this list just briefly to give some feedback and input on this thread on behalf of Software Freedom Conservancy, since we were mentioned multiple times in this thread. I suspect any conversation about how Conservancy and GCC might work together should be off-list or another list, and I

Update to GCC copyright assignment policy

> Sent: Friday, June 04, 2021 at 2:45 AM > From: "Giacomo Tesio" > To: "Jakub Jelinek" > Cc: gcc@gcc.gnu.org > Subject: Re: Update to GCC copyright assignment policy > > On Thu, 3 Jun 2021 16:14:15 +0200 Jakub Jelinek wrote: > > > Because it makes no sense > > A change in the copyright policie

Re: Update to GCC copyright assignment policy

On Thu, Jun 3, 2021 at 10:46 AM Giacomo Tesio wrote: > > I would have really appreciated if the GCC SC had announced such change > for the upcoming GCC 12 while sticking to the old policy in GCC 11. > That is how I was thinking of the change, but I agree that it needs clarification. Jason

Re: Mailing list reconfiguration: VERP Sender: header affected

| From: Martin Liška | Which we recommend in the ection Filtering here: | https://gcc.gnu.org/lists.html Thanks for the useful information. That document suggests: * ^List-Id: .*<.*.gcc.gnu.org>$ Surely this should be: * ^List-Id: .*<.*.gcc\.gnu\.org>$

Re: Update to GCC copyright assignment policy

On Thu, 3 Jun 2021 16:14:15 +0200 Jakub Jelinek wrote: > Because it makes no sense A change in the copyright policies and ownership of a project is usually seen as a very big change, so much that usually the project change its whole name, not just its major version. > doing a GCC release is lots

Re: Update to GCC copyright assignment policy

On Thu, Jun 03, 2021 at 04:07:07PM +0200, Giacomo Tesio wrote: > On Thu, 3 Jun 2021 15:02:16 +0200 Jakub Jelinek wrote: > > > On Thu, Jun 03, 2021 at 02:35:51PM +0200, Giacomo Tesio wrote: > > > Is it possible to release a new version for the last commit that > > > only includes changes under FSF

Re: Update to GCC copyright assignment policy

Hi Jakub, On Thu, 3 Jun 2021 15:02:16 +0200 Jakub Jelinek wrote: > On Thu, Jun 03, 2021 at 02:35:51PM +0200, Giacomo Tesio wrote: > > Is it possible to release a new version for the last commit that > > only includes changes under FSF copyright, possibly deferring the > > introduction of non-fsf

Re: Update to GCC copyright assignment policy

On Thu, Jun 03, 2021 at 02:35:51PM +0200, Giacomo Tesio wrote: > > The GCC Steering Committee has decided to relax the requirement to > > assign copyright for all changes to the Free Software Foundation. GCC > > will continue to be developed, distributed, and licensed under the GNU > > General Pub

Re: Update to GCC copyright assignment policy

Hello GCC developers, On Tue, 1 Jun 2021 10:00:06 -0400 David Edelsohn via Gcc wrote: > The GCC Steering Committee has decided to relax the requirement to > assign copyright for all changes to the Free Software Foundation. GCC > will continue to be developed, distributed, and licensed under the

Re: GCC documentation: porting to Sphinx

On 6/2/21 6:44 PM, Joseph Myers wrote: On Wed, 2 Jun 2021, Joel Sherrill wrote: For RTEMS, we switched from texinfo to Sphinx and the dependency on Python3 for Sphinx has caused a bit of hassle. Is this going to be an issue for GCC? What Sphinx (and, thus, Python) versions does the GCC manual

Re: GCC Rust monthly call

Hi everyone, Just a reminder that tomorrow is the community call: at 10am utc+1. The agenda so far is detailed within: https://hackmd.io/rBFlwl_9TkWLox-X6jyxDg The call will be hosted on Jitsi, here is the link we will use: https://meet.jit.si/259057065581073 Thanks --Phil On Mon, 31 May 2021

Re: Mailing list reconfiguration: VERP Sender: header affected

On 6/2/21 4:52 PM, Frank Ch. Eigler via Gcc wrote: If you use Sender:-based filtering for sorting your incoming email stream, I suggest switching to observing List-Id: instead, or else using a regexp/substring style of Sender: matching. Which we recommend in the ection Filtering here: https://g

Re: GCC documentation: porting to Sphinx

On 6/2/21 10:41 PM, Martin Sebor wrote: On 5/31/21 7:25 AM, Martin Liška wrote: Hello. I've made quite some progress with the porting of the documentation and I would like to present it to the community now: https://splichal.eu/scripts/sphinx/ Hello. Thank you for the review. Just a few

Incorrect linker paths for building gcc on 32-bit PowerPC

Hi! I'm currently building GCC from git on various Debian targets to help with the gccrs development effort a bit. On 32-bit PowerPC, I have run into a problem which seems to be related to Multi-Arch (see below). I have already the patch gcc-multiarch.diff that Debian is shipping and passing --en