Re: progress update

Hi, On Tue, Jun 15 2021, David Malcolm via Gcc wrote: > [...] > > Are you perhaps building the first stage using clang, or a very old > gcc? That would likely generate very different debuginfo, which might > explain the differences in behavior that you're seeing in gdb. > > If I run into proble

Re: [ranger-tech] How to use ranges within any pass with get_range_query()

Hi, On Thu, Jun 10 2021, Aldy Hernandez via Gcc wrote: > As part of the ranger development we have found that there are various > pieces of the infrastructure that can be used independently, and we’d > like to document them in the hopes that they are useful to others. We > will be contributing

Re: git gcc-commit-mklog doesn't extract PR number to ChangeLog

On Wed, 16 Jun 2021 at 03:03, Martin Sebor wrote: > > On 6/15/21 6:56 PM, Hans-Peter Nilsson wrote: > > On Fri, 11 Jun 2021, Martin Sebor via Gcc wrote: > > > >> On 6/11/21 11:32 AM, Jonathan Wakely wrote: > >>> On Fri, 11 Jun 2021 at 18:02, Martin Sebor wrote: > My objection is to making our

Re: git gcc-commit-mklog doesn't extract PR number to ChangeLog

On 6/15/21 9:42 PM, Jason Merrill wrote: On Tue, Jun 15, 2021 at 10:04 PM Martin Sebor via Gcc > wrote: On 6/15/21 6:56 PM, Hans-Peter Nilsson wrote: > On Fri, 11 Jun 2021, Martin Sebor via Gcc wrote: > >> On 6/11/21 11:32 AM, Jonathan Wakely wrote:

[RISCV][CANCELLED] RISC-V GNU Toolchain Biweekly Sync-up call (June 17, 2021)

Hi all, We will skip tomorrow's RISC-V GNU Biweekly meeting. Not so many topics were collected. No big progress on CI in the past two weeks, for I was preparing for the upcoming RISC-V World Conference China 2021 (RVWC2021). Hopefully I will have more time on CI after June 27. -- Best wishes, W

GCC trunk commit a325bdd195ee96f826b208c3afb9bed2ec077e12

Hi all, I recently did a search on a git log of gcc trunk looking for a particular commit of mine, so was searching for my name, and I came across a commit from Uroš that lists me as the Author. I did not author that commit and talking with Uroš offline, he assures me that he didn't use --author

Re: GCC trunk commit a325bdd195ee96f826b208c3afb9bed2ec077e12

>Is there someone who an dig into the commit below >and try to find out how the author field was incorrectly set? That gets set when the local commit is done, before pushing it to the server. I don't think there's any way to find out how/why that happened after the fact. You did author the commit

Re: GCC trunk commit a325bdd195ee96f826b208c3afb9bed2ec077e12

在 2021-06-16 23:22, Jonathan Wakely via Gcc 写道: Is there someone who an dig into the commit below and try to find out how the author field was incorrectly set? That gets set when the local commit is done, before pushing it to the server. I don't think there's any way to find out how/why that ha

Re: Build failure due to format-truncation

On 6/13/21 11:48 AM, José Rui Faustino de Sousa via Gcc wrote: Hi All! While building I started to get this error: ../../gcc-master/gcc/opts.c: In function ‘void print_filtered_help(unsigned int, unsigned int, unsigned int, unsigned int, gcc_options*, unsigned int)’: ../../gcc-master/gcc/opt

Re: docs: Unification of "enabled by default at -O{,1}

On 6/11/21 6:53 AM, Martin Liška wrote: Hello. First, note that -O is equal to -O1 :) I noticed we don't use it consistently in documentation: $ git grep 'at.*-O1}' | cat gcc/ada/gnat_ugn.texi:pick it based on the optimization level: 1 for @code{-O1}, @code{-O2} or ... Is the later (and

Re: Build failure due to format-truncation

On 16/06/21 16:53, Martin Sebor wrote: -fstrict-overflow isn't related to the warning or to sprintf (it controls whether signed integer overflow is considered undefined). The warning above tells you that if help points to a string that's 255 characters long the snprintf output will be truncated.

Re: git gcc-commit-mklog doesn't extract PR number to ChangeLog

On Tue, 15 Jun 2021, Martin Sebor wrote: > On 6/15/21 6:56 PM, Hans-Peter Nilsson wrote: > > On Fri, 11 Jun 2021, Martin Sebor via Gcc wrote: > > > > > On 6/11/21 11:32 AM, Jonathan Wakely wrote: > > > > On Fri, 11 Jun 2021 at 18:02, Martin Sebor wrote: > > > > > My objection is to making our polic

Re: GCC trunk commit a325bdd195ee96f826b208c3afb9bed2ec077e12

On Wed, Jun 16, 2021 at 6:08 PM Liu Hao wrote: > > 在 2021-06-16 23:22, Jonathan Wakely via Gcc 写道: > >> Is there someone who an dig into the commit below > >> and try to find out how the author field was incorrectly set? > > > > That gets set when the local commit is done, before pushing it to the

Re: GCC trunk commit a325bdd195ee96f826b208c3afb9bed2ec077e12

On 6/16/21 1:32 PM, Uros Bizjak wrote: > On Wed, Jun 16, 2021 at 6:08 PM Liu Hao wrote: >> It looks like Uroš was on 00d07ec6e12, committed his changes mistakenly with >> `git commit --amend` >> (which changed the commit message but did not reset the author), then >> rebased the modified commit

Re: Build failure due to format-truncation

On 6/16/21 11:21 AM, José Rui Faustino de Sousa wrote: On 16/06/21 16:53, Martin Sebor wrote: -fstrict-overflow isn't related to the warning or to sprintf (it controls whether signed integer overflow is considered undefined). The warning above tells you that if help points to a string that's 25

Re: git gcc-commit-mklog doesn't extract PR number to ChangeLog

On 6/15/21 11:42 PM, Jason Merrill wrote: On Tue, Jun 15, 2021 at 10:04 PM Martin Sebor via Gcc > wrote: On 6/15/21 6:56 PM, Hans-Peter Nilsson wrote: > On Fri, 11 Jun 2021, Martin Sebor via Gcc wrote: > >> On 6/11/21 11:32 AM, Jonathan Wakely wrote:

The official glibc IRC channel is now on OFTC as #glibc.

Community, The official glibc IRC channel is now on OFTC as #glibc. gcc developers, please feel free to visit #glibc :-) We also have an unofficial IRC channel #glibc on Libera.Chat -- Cheers, Carlos.

Re: git gcc-commit-mklog doesn't extract PR number to ChangeLog

On 6/16/21 2:49 PM, Jason Merrill wrote: On 6/15/21 11:42 PM, Jason Merrill wrote: On Tue, Jun 15, 2021 at 10:04 PM Martin Sebor via Gcc > wrote:     On 6/15/21 6:56 PM, Hans-Peter Nilsson wrote: > On Fri, 11 Jun 2021, Martin Sebor via Gcc wrote: > >> On 6

Aldy Hernandez and Andrew MacLeod as VRP maintainers

I am pleased to announce that the GCC Steering Committee has appointed Aldy Hernandez and Ian MacLeod as maintainers for the VRP subsystem (EVRP, VRP, Ranger). Aldy/Andrew, please update the MAINTAINERS file appropriately. Thanks, jeff

Re: git gcc-commit-mklog doesn't extract PR number to ChangeLog

On Wed, Jun 16, 2021 at 5:46 PM Martin Sebor wrote: > On 6/16/21 2:49 PM, Jason Merrill wrote: > > On 6/15/21 11:42 PM, Jason Merrill wrote: > >> On Tue, Jun 15, 2021 at 10:04 PM Martin Sebor via Gcc >> > wrote: > >> > >> On 6/15/21 6:56 PM, Hans-Peter Nilsson wrote:

Re: git gcc-commit-mklog doesn't extract PR number to ChangeLog

On 6/16/21 5:45 PM, Jason Merrill wrote: On Wed, Jun 16, 2021 at 5:46 PM Martin Sebor > wrote: On 6/16/21 2:49 PM, Jason Merrill wrote: > On 6/15/21 11:42 PM, Jason Merrill wrote: >> On Tue, Jun 15, 2021 at 10:04 PM Martin Sebor via Gcc mailto:gcc@gcc.g

Re: Build failure due to format-truncation

On 16/06/21 20:37, Martin Sebor wrote: I don't really think the warning is doing anything wrong I completely agree. I am not complaining about the warning, I am complaining that there is code in gcc which raises this warning and breaks the build. I was assuming that this was being triggere

Re: git gcc-commit-mklog doesn't extract PR number to ChangeLog

On 6/16/21 8:17 PM, Martin Sebor wrote: On 6/16/21 5:45 PM, Jason Merrill wrote: On Wed, Jun 16, 2021 at 5:46 PM Martin Sebor > wrote:     On 6/16/21 2:49 PM, Jason Merrill wrote: > On 6/15/21 11:42 PM, Jason Merrill wrote: >> On Tue, Jun 15, 2021 at 10:04 PM

Re: git gcc-commit-mklog doesn't extract PR number to ChangeLog

On 6/16/21 6:40 PM, Jason Merrill wrote: On 6/16/21 8:17 PM, Martin Sebor wrote: On 6/16/21 5:45 PM, Jason Merrill wrote: On Wed, Jun 16, 2021 at 5:46 PM Martin Sebor > wrote:     On 6/16/21 2:49 PM, Jason Merrill wrote: > On 6/15/21 11:42 PM, Jason Merrill wrote:

Re: git gcc-commit-mklog doesn't extract PR number to ChangeLog

On 6/16/21 9:01 PM, Martin Sebor wrote: On 6/16/21 6:40 PM, Jason Merrill wrote: On 6/16/21 8:17 PM, Martin Sebor wrote: On 6/16/21 5:45 PM, Jason Merrill wrote: On Wed, Jun 16, 2021 at 5:46 PM Martin Sebor > wrote:     On 6/16/21 2:49 PM, Jason Merrill wrote: >