Re: Build failure due to format-truncation

2021-06-20 Thread José Rui Faustino de Sousa via Gcc
On 18/06/21 00:05, Martin Sebor wrote: Right, with -O0 we understand why it happens. I think I have found a minimal way to reproduce the build failure: make BOOT_CFLAGS="-O0" bootstrap No environment variables set. Setting CFLAGS, CXXFLAGS or both does not seem to have any effect. Addition

Re: Build failure due to format-truncation

2021-06-17 Thread Martin Sebor via Gcc
On 6/17/21 5:04 PM, José Rui Faustino de Sousa wrote: On 17/06/21 20:51, Martin Sebor wrote: What stage does this happens in, and if stage 1, what is the system compiler? > I am not sure if this happens also in the earlier stages, I would have to do a complete rebuild and that would take so

Re: Build failure due to format-truncation

2021-06-17 Thread José Rui Faustino de Sousa via Gcc
On 17/06/21 20:51, Martin Sebor wrote: What stage does this happens in, and if stage 1, what is the system compiler? > I am not sure if this happens also in the earlier stages, I would have to do a complete rebuild and that would take some time. I have built gcc using an altered "opts.c" so

Re: Build failure due to format-truncation

2021-06-17 Thread Martin Sebor via Gcc
On 6/16/21 6:26 PM, José Rui Faustino de Sousa wrote: 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 t

Re: Build failure due to format-truncation

2021-06-16 Thread José Rui Faustino de Sousa via Gcc
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: Build failure due to format-truncation

2021-06-16 Thread Martin Sebor via Gcc
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: Build failure due to format-truncation

2021-06-16 Thread José Rui Faustino de Sousa via Gcc
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: Build failure due to format-truncation

2021-06-16 Thread Martin Sebor via Gcc
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

Build failure due to format-truncation

2021-06-13 Thread José Rui Faustino de Sousa via Gcc
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/opts.c:1497:26: error: ‘ ’ directive output may be truncated wri