Re: typeof and operands in named address spaces

2020-11-09 Thread Peter Zijlstra
On Mon, Nov 09, 2020 at 11:50:15AM -0800, Nick Desaulniers wrote: > On Mon, Nov 9, 2020 at 11:46 AM Segher Boessenkool > wrote: > > > > On Mon, Nov 09, 2020 at 01:47:13PM +0100, Peter Zijlstra wrote: > > > > > > + lots of people and linux-toolchains > > > > > > On Wed, Nov 04, 2020 at 07:31:42PM +

Re: typeof and operands in named address spaces

2020-11-09 Thread Peter Zijlstra
On Mon, Nov 09, 2020 at 01:38:51PM -0600, Segher Boessenkool wrote: > On Mon, Nov 09, 2020 at 01:47:13PM +0100, Peter Zijlstra wrote: > > > > + lots of people and linux-toolchains > > > > On Wed, Nov 04, 2020 at 07:31:42PM +0100, Uros Bizjak wrote: > > > Hello! > > > > > > I was looking at the r

cache optimization through samping hardware event

2020-11-09 Thread 172060045
Hi, Recently, I was interested in GCC AutoFDO optimization, which works by sampling specific PMU event on production machines and using those profiles to guide optimization. In this way, information such as cache miss can also be obtained through sampling, so can we implement feedback-directed

Re: Detect EAF flags in ipa-modref

2020-11-09 Thread Jan Hubicka
Hi, this is updated patch for autodetection of EAF flags. Still the goal is to avoid fancy stuff and get besic logic in place (so no dataflow, no IPA propagation, no attempts to handle trickier cases). There is one new failure ./gcc/testsuite/gcc/gcc.sum:FAIL: gcc.dg/sso/t2.c -Wno-scalar-stora

Re: gcc/DATESTAMP not updated any longer

2020-11-09 Thread Jakub Jelinek via Gcc
On Mon, Nov 09, 2020 at 08:57:48AM +0100, Martin Liška wrote: > On 11/6/20 8:59 PM, Jakub Jelinek wrote: > > I think I'll work with Martin early next week to think about further spots > > to add logging, so we narrow down where it is still called and where it > > isn't. > > Hello. > > I'm suggest

Re: typeof and operands in named address spaces

2020-11-09 Thread Nick Desaulniers via Gcc
On Mon, Nov 9, 2020 at 11:46 AM Segher Boessenkool wrote: > > On Mon, Nov 09, 2020 at 01:47:13PM +0100, Peter Zijlstra wrote: > > > > + lots of people and linux-toolchains > > > > On Wed, Nov 04, 2020 at 07:31:42PM +0100, Uros Bizjak wrote: > > > Hello! > > > > > > I was looking at the recent linu

Re: typeof and operands in named address spaces

2020-11-09 Thread Segher Boessenkool
On Mon, Nov 09, 2020 at 01:47:13PM +0100, Peter Zijlstra wrote: > > + lots of people and linux-toolchains > > On Wed, Nov 04, 2020 at 07:31:42PM +0100, Uros Bizjak wrote: > > Hello! > > > > I was looking at the recent linux patch series [1] where segment > > qualifiers (named address spaces) wer

Gcov info registration without constructor?

2020-11-09 Thread Sebastian Huber
Hello, I would like to use the -ftest-coverage -fprofile-arcs support on a bare metal system (no operating system or very early stages in the system startup). In this environment I cannot use the gcov info registration via a constructor and __gcov_init(), because there may be some other (more

Detect EAF flags in ipa-modref

2020-11-09 Thread Jan Hubicka
> > > > Yep, i am not arguing for eliminating special case of memcpy (because we > > have the additional info that it only copies pointers from *src to > > *dest). > > > > However I find current definition of EAF_NOESCAPE bit hard to handle in > > modref, since naturally it is quite reliable to t

Re: typeof and operands in named address spaces

2020-11-09 Thread Peter Zijlstra
+ lots of people and linux-toolchains On Wed, Nov 04, 2020 at 07:31:42PM +0100, Uros Bizjak wrote: > Hello! > > I was looking at the recent linux patch series [1] where segment > qualifiers (named address spaces) were introduced to handle percpu > variables. In the patch [2], the author mention

Re: Definition of EAF_NOESCAPE and fnspec strings

2020-11-09 Thread Richard Biener
On Mon, 9 Nov 2020, Jan Hubicka wrote: > > > But it also means that some of our FNSPECs are wrong now. I wonder if we > > > can > > > split this porperty to two different flags like EAF_NOEASCAPE and > > > EAF_INDIRECT_NOESCAPE? > > > > Note that EAF_NOESCAPE allows "escaping" to the return val

Odd hash_table::expand behavior

2020-11-09 Thread Richard Biener
I'm investigating an issue I run into with using changes of size () as an indicator of hash-table re-allocation through expand (). This doesn't work when ::expand computes the same size as before since it then still happily re-allocates. To complicate this ::expand has its own heuristic when to

Embedded Real-Time Operating Systems for the IoT Market Analysis: Here's the One Report That You Must Share With Your Management Team

2020-11-09 Thread garemwinmark via Gcc
Hello Have a nice day ! This is JoJo from WMResearch. We recently published a new market research report: < Global Embedded Real-Time Operating Systems for the IoT Market Research Report 2015-2020>and kindly let us know if you are interested in it. If you are interested in getting more det

Re: Definition of EAF_NOESCAPE and fnspec strings

2020-11-09 Thread Jan Hubicka
> > But it also means that some of our FNSPECs are wrong now. I wonder if we > > can > > split this porperty to two different flags like EAF_NOEASCAPE and > > EAF_INDIRECT_NOESCAPE? > > Note that EAF_NOESCAPE allows "escaping" to the return value (see > handle_rhs_call). I guess for simplicity