gcc-8-20200430 is now available

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

GCC 10.1 Release Candidate available from gcc.gnu.org

The first release candidate for GCC 10.1 is available from https://gcc.gnu.org/pub/gcc/snapshots/10.1.0-RC-20200430/ ftp://gcc.gnu.org/pub/gcc/snapshots/10.1.0-RC-20200430 and shortly its mirrors. It has been generated from git revision r10-8080-g591d857164c37cd0bb96da2a293148e01f280e0f. I

Re: [libgomp] Ask for help on an improvement for synchronization overhead

On Thu, Apr 30, 2020 at 05:37:26PM -0300, Adhemerval Zanella via Gcc wrote: > Hi all, I would like to check if someone could help me figure out > an issue I am chasing on a libgomp patch intended to partially > address the issue described at BZ#79784. > > I have identified that one of the bottlen

[libgomp] Ask for help on an improvement for synchronization overhead

Hi all, I would like to check if someone could help me figure out an issue I am chasing on a libgomp patch intended to partially address the issue described at BZ#79784. I have identified that one of the bottlenecks is the global barrier used on both thread pool and team which causes a lof of ca

GCC 11.0.0 Status Report (2020-04-30)

Status == The trunk has branched for the GCC 10 release and is now open again for general development, stage 1. Please consider not disrupting it too much during the RC phase of GCC 10 so it is possible to test important fixes for 10.1 on it. Quality Data Priority #

GCC 10.0.1 Status Report (2019-04-30)

Status == We have reached zero P1 regressions today and releases/gcc-10 branch has been created; GCC 10.1-rc1 will be built and announced later tonight or tomorrow. The branch is now frozen for blocking regressions and documentation fixes only, all changes to the branch require a RM approval

Re: Automatically generated ChangeLog files - script

On Thu, Apr 30, 2020 at 05:14:34PM +0200, Martin Liška wrote: > On 4/30/20 3:45 PM, Jakub Jelinek wrote: > > If this is what is really created, then for the new file, missing * space, > > gcc/testsuite/ that shouldn't be there and missing PR c++/94546 line above > > it. > > I've just fixed all the

Re: Automatically generated ChangeLog files - script

On 4/30/20 3:45 PM, Jakub Jelinek wrote: If this is what is really created, then for the new file, missing * space, gcc/testsuite/ that shouldn't be there and missing PR c++/94546 line above it. I've just fixed all these, thanks! About the 'PR c++/94546': it's mentioned in context of 'gcc/cp/C

Re: Automatically generated ChangeLog files - script

On Thu, Apr 30, 2020 at 03:29:10PM +0200, Martin Liška wrote: > $ ./changelog.py > patches/1957-c-generic-lambda-forwarding-function-PR94546.patch > OK > -- gcc/cp/ChangeLog -- > 2020-04-22 Jason Merrill > > PR c++/94546 > * pt.c (register_parameter_specializations): If the

Automatically generated ChangeLog files - script

Hello. Based on the initial discussion with Richi and Jakub, we would like to remove need to update ChangeLog files with each git commit. Instead, a script will be used to extract ChangeLog entries from a git commit messages. I've started with extraction of ~2K commits since we switched to git (

[Inline assembly] thought on the memory

Hi everyone, I am looking for some clarification about how are working the memory operands, especially when the constraint allows memory only (eg. "m"). Please note that in a lesser extent, I know (by looking the gcc sources) how the things are currently working but I wonder if it is a design

RE: Should ARMv8-A generic tuning default to -moutline-atomics

Hi Michael, > -Original Message- > From: Gcc On Behalf Of Michael Matz > Sent: 30 April 2020 12:10 > To: Florian Weimer > Cc: gcc@gcc.gnu.org; nmeye...@amzn.com > Subject: Re: Should ARMv8-A generic tuning default to -moutline-atomics > > Hello, > > On Wed, 29 Apr 2020, Florian Weimer

Re: Should ARMv8-A generic tuning default to -moutline-atomics

Hello, On Wed, 29 Apr 2020, Florian Weimer via Gcc wrote: > Distributions are receiving requests to build things with > -moutline-atomics: > > > > Should this be reflected in the GCC upstream defaults for ARMv8-A > generic tuning? It