Re: 'I' and 'U' fn spec specifiers

2024-11-15 Thread Richard Biener
On Fri, 15 Nov 2024, Jₑₙₛ Gustedt wrote: > Hello Richard, > > On Fri, 15 Nov 2024 15:00:44 +0100 (CET), Richard Biener wrote: > > > fnspec was originally introduced for PTA, but 'I' and 'U' given the > > pointers escape, do not help PTA, as soon as pointers escape all > > (most) bets are lost. >

Re: 'I' and 'U' fn spec specifiers

2024-11-15 Thread Jₑₙₛ Gustedt
Hello Richard, On Fri, 15 Nov 2024 15:00:44 +0100 (CET), Richard Biener wrote: > fnspec was originally introduced for PTA, but 'I' and 'U' given the > pointers escape, do not help PTA, as soon as pointers escape all > (most) bets are lost. > > So where and how exactly do you plan to use those?

Re: 'I' and 'U' fn spec specifiers

2024-11-15 Thread Richard Biener
On Fri, 15 Nov 2024, Jan Hubicka wrote: > Hi, > To implement pointer parameters reproducible and unsequenced I would like to > use fnspec built at callgraph construction time. Pointer parameters are > either > const or non-const. After discussion with Jens, I now understand that memory > pointe

'I' and 'U' fn spec specifiers

2024-11-15 Thread Jan Hubicka
Hi, To implement pointer parameters reproducible and unsequenced I would like to use fnspec built at callgraph construction time. Pointer parameters are either const or non-const. After discussion with Jens, I now understand that memory pointed to by const pointers can only be read directly and n