Re: Possible suboptimal code generated in 32-bit ABI mode

On Sun, Nov 19, 2017 at 5:35 PM, Richard Bradfield wrote: > On Sun, Nov 19, 2017 at 04:19:45PM +, bradf...@fstab.me wrote: >> >> For reference, I am compiling everything using gcc trunk, at commit >> 254929 from Sun Nov 19, and I am benchmarking on a Skylake i7-6700K >> at 4.0GHz. > > > And so

Re: Finding all CALL_EXPR tree nodes during GENERIC

On Sun, Nov 19, 2017 at 9:27 PM, Katsunori Kumatani wrote: > Yes, it seems walk_tree does the job, I was probably doing something > wrong before. Thank you. > > I have a question about it. Am I correct in assuming I only have to > check the subtrees of nodes that satisfy EXPR_P? So for nodes that

GCC 8.0.0 Status Report (2017-11-20)

Status == GCC 8 is now in Stage 3 which means open for general bugfixing. As usual we're now in a short period where posted but not yet reviewed feature patches can be accepted. As time goes by even those will be no longer appropriate. As usual in this time not all regressions have been pr

Re: Please review writeup for fixing PR 78809 (inline strcmp for small constant strings)

> On Nov 17, 2017, at 5:54 PM, Martin Sebor wrote: > >> >> for the safety checking purpose, when we try to convert >> >> __builtin_strcmp(s, "abc") != 0 >> >> to >> >> __builtin_memcmp (s, “abc”, 4) != 0 >> >> we have to make sure that the size of variable “s” is larger than “4”. > > Presu

futurist.co.in

Hi , We are own this domain name, have you made a decision to purchase it ? Looking forward to your reply. My admin e-mail: 2398...@qq.com Best regards, Alice

Re: Please review writeup for fixing PR 78809 (inline strcmp for small constant strings)

> On Nov 17, 2017, at 7:32 PM, Jeff Law wrote: > > On 11/17/2017 03:45 PM, Qing Zhao wrote: do you think using this routine is good? or do you have other suggestions (since I am still not very familiar with the internals of GCC, might not find the best available one now…) >>> The

Fail to compile GDB with recent GCC trunk (-Werror=stringop-overflow=, -Werror=stringop-truncation)

Hi, I failed to compile GDB with GCC trunk (8.0.0 20171117) because of some -Werror=stringop-overflow= and -Werror=stringop-truncation warnings. Some of them are not necessary to me, 1. ../../binutils-gdb/gdb/python/py-gdb-readline.c:79:15: error: ‘char* strncpy(char*, const char*, size_t)’ outp

Re: Please review writeup for fixing PR 78809 (inline strcmp for small constant strings)

> On Nov 17, 2017, at 7:39 PM, Jeff Law wrote: > >>> >> >> thanks for the info, Martin. >> >> In my case, it’s the size of “100” cannot be collected in the >> MINMAXLEN[1] for the string “s”. >> >> I need to make sure that the size of variable string s is larger than >> the size of constant

Re: Fail to compile GDB with recent GCC trunk (-Werror=stringop-overflow=, -Werror=stringop-truncation)

On 11/20/17, Yao Qi wrote: > > Hi, > I failed to compile GDB with GCC trunk (8.0.0 20171117) because of some > -Werror=stringop-overflow= and -Werror=stringop-truncation warnings. > Some of them are not necessary to me, > > 1. ../../binutils-gdb/gdb/python/py-gdb-readline.c:79:15: error: ‘char* >

Re: Fail to compile GDB with recent GCC trunk (-Werror=stringop-overflow=, -Werror=stringop-truncation)

On 11/20/2017 08:51 AM, Yao Qi wrote: Hi, I failed to compile GDB with GCC trunk (8.0.0 20171117) because of some -Werror=stringop-overflow= and -Werror=stringop-truncation warnings. Some of them are not necessary to me, I have the attached patch for two of these but I have been waiting to sub

Re: Fail to compile GDB with recent GCC trunk (-Werror=stringop-overflow=, -Werror=stringop-truncation)

On 17-11-20 09:33:46, Martin Sebor wrote: > On 11/20/2017 08:51 AM, Yao Qi wrote: > > > >Hi, > >I failed to compile GDB with GCC trunk (8.0.0 20171117) because of some > >-Werror=stringop-overflow= and -Werror=stringop-truncation warnings. > >Some of them are not necessary to me, > > I have the at