Hi Basile,
> On 28 Jun 2024, at 11:11, Basile Starynkevitch
> wrote:
> Iain Sandoe wrote:
>
>> If I declare a function __attribute__((noipa, optimize (“-O0”))), I was
>> kinda expecting that it would not be optimized at all ..
>>
>> however it does not seem to prevent functions called by it
Hello
Iain Sandoe wrote:
If I declare a function __attribute__((noipa, optimize (“-O0”))), I was kinda
expecting that it would not be optimized at all ..
however it does not seem to prevent functions called by it from being inlined
into its body ..
I would suggest coding your GCC plugin to
> On 27 Jun 2024, at 20:06, Richard Biener via Gcc wrote:
>> Am 27.06.2024 um 19:43 schrieb Iain Sandoe :
>>> On 27 Jun 2024, at 14:51, Iain Sandoe wrote:
>>>
>>> If I declare a function __attribute__((noipa, optimize (“-O0”))), I was
>>> kinda expecting that it would not be optimized at all
> Am 27.06.2024 um 19:43 schrieb Iain Sandoe :
>
>
>> On 27 Jun 2024, at 14:51, Iain Sandoe wrote:
>>
>> If I declare a function __attribute__((noipa, optimize (“-O0”))), I was
>> kinda expecting that it would not be optimized at all ..
>>
>> however it does not seem to prevent functions
> On 27 Jun 2024, at 14:51, Iain Sandoe wrote:
>
> If I declare a function __attribute__((noipa, optimize (“-O0”))), I was kinda
> expecting that it would not be optimized at all ..
>
> however it does not seem to prevent functions called by it from being inlined
> into its body ..
>
> am
Hello
If I declare a function __attribute__((noipa, optimize (“-O0”))), I was kinda
expecting that it would not be optimized at all ..
however it does not seem to prevent functions called by it from being inlined
into its body ..
am I missing some additional constraint that should be added?
