Re: gccadmin hooks: make it a public git repo

PING^1 On 1/14/21 10:02 AM, Martin Liška wrote: On 1/13/21 6:00 PM, Joseph Myers wrote: I'm fine with having it set up with a public repository. Ok, can you please do it Joseph? If you have a public (bare) repository that would of course need to have its own hooks to update the (non-bare) h

Re: [PATCH] Try LTO partial linking. (Was: Speed of compiling gimple-match.c)

On 5/21/21 2:35 PM, David Edelsohn wrote: Please remember that not all targets support LTO so a fallback to a non-partial-LTO build needs to be provided and automatically invoked for those targets. Sure, for now it's definitely going to be a opt-in, enabled by something like: make PARTIAL_LTO=1

safety command-line options

I wonder if we could get a nice short command-line option for recommended safety/security related flags. We have -Ox for optimization and -Wall for a useful set of recommended warnings. I am thinking about options such as -ftrapv -fsanitize=undefined -fsanitize-undefined-trap-on-error -fstack

Re: Welcome GCC GSoC 2021 participants

Hello, On Sun, May 23 2021, Ankur Saini wrote: > Hello, > >> On 18-May-2021, at 9:52 PM, Martin Jambor wrote: >> >> All accepted students which do not already have one must request a >> copyright assignment[1] as soon as possible. Please email the >> following information to ass...@gnu.org and

Fw: Regarding __gcov_dump and __gcov_reset usage

Adding gcc mailing list for the clarification. Thank you team !  From: "Gejoe Daniel" Sent: Mon, 24 May 2021 15:02:12 To: "gcc-h...@gcc.gnu.org" Subject: Re: Regarding __gcov_dump and __gcov_reset usage Hi team, Any info/reply ? Thanking you in adva

GCC Rust git branch

Hi everyone, As some of you might know, I have been working on GCC Rust over on GitHub https://github.com/Rust-GCC/gccrs. As the project is moving forward and enforcing GCC copyright assignments for contributors, I would like to create a branch on the GCC git repo to show the intention to be upstr

Re: Fw: Regarding __gcov_dump and __gcov_reset usage

On 5/24/21 1:44 PM, Gejoe Daniel via Gcc wrote: Adding gcc mailing list for the clarification. Thank you team !  From: "Gejoe Daniel" Sent: Mon, 24 May 2021 15:02:12 To: "gcc-h...@gcc.gnu.org" Subject: Re: Regarding __gcov_dump and __gcov_reset usage

Re: GCC Rust git branch

On Mon, 24 May 2021, Philip Herron wrote: > remote: error: hook declined to update refs/heads/gccrs refs/heads/gccrs doesn't match the branch naming conventions as documented at https://gcc.gnu.org/git.html (where you'd use refs/heads/devel/* for shared development branches), so if you hadn't h

Re: GCC Rust git branch

Hi Philip, On Mon, May 24, 2021 at 02:24:13PM +0100, Philip Herron wrote: > As some of you might know, I have been working on GCC Rust over on > GitHub https://github.com/Rust-GCC/gccrs. As the project is moving > forward and enforcing GCC copyright assignments for contributors, I > would like to

Re: safety command-line options

On 5/24/21 2:18 AM, Uecker, Martin wrote: I wonder if we could get a nice short command-line option for recommended safety/security related flags. We have -Ox for optimization and -Wall for a useful set of recommended warnings. I am thinking about options such as -ftrapv -fsanitize=undefined

https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gfortran/

Hi folks, some more suggestions for corrections in the onlinedocs: https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gfortran/GERROR.html#GERROR RESULT "Shall of type CHARACTER and of default" --> "Shall BE of ... default KIND." https://gcc.gnu.org/onlinedocs/gcc-11.1.0/gfortran/GETARG.html#GETA

RE: [EXTERNAL] Re: State of AutoFDO in GCC

Thank you Wei. Looks like something is still missing. This time perf_data.pb.h is not found. I'm getting the error below (on Ubuntu 18.04 with cmake 3.12.1): eugene@eugene-Virtual-Machine:~/autofdo1/build$ ninja [1/241] Building CXX object CMakeFiles/dump_gcov_lib.dir/profile.cc.o FAILED: CMakeFi

Re: [EXTERNAL] Re: State of AutoFDO in GCC

Sorry, I added dependency for create_gcov but missed it for dump_gcov. Fixed it at https://github.com/google/autofdo/commit/6ca36cdc30986f13583a3aef3e27746ca4fc5bf6 . Thanks, Wei. On Mon, May 24, 2021 at 6:39 PM Eugene Rozenfeld < eugene.rozenf...@microsoft.com> wrote: > Thank you Wei. Looks lik

RE: [EXTERNAL] Re: State of AutoFDO in GCC

That fixed the error I saw before but the build still fails. The errors start with eugene@eugene-Virtual-Machine:~/autofdo1/build$ ninja [2/217] Building CXX object CMakeFiles/quipper_perf.dir/third_party/perf_data_converter/src/quipper/huge_page_deducer.cc.o FAILED: CMakeFiles/quipper_perf.dir

Re: [EXTERNAL] Re: State of AutoFDO in GCC

It isn't exposed on my platform either. Looks like a bug in perf_data_converter (i.e., quipper). Could you try adding #include in third_party/perf_data_converter/src/quipper/huge_page_deducer.cc and see if it fixes the problem? If it works, I will need to file a bug against perf_data_converter. T

Re: GCC 9.4 Status Report (2021-05-19), branch frozen for release

On Fri, 21 May 2021, Jason Merrill wrote: > Sorry, just pushed 3 patches before I noticed this. They're safe but not > critical, should I back them out? They look safe indeed, so let's keep them in. Richard. > On Wed, May 19, 2021 at 4:06 AM Richard Biener wrote: > > > > > Status > > ==