Re: avoiding builtin memset

[Simon Wright <simon@pushface.org>]

"J-P. Rosen" <rosen@adalog.fr> writes:

> Le 27/04/2017 à 02:22, Jere a écrit :
>>> 	For Element of Memory loop
>>> 	    Element := Value;
>>> 	end loop;
>>
>> I'll be honest, I wasn't expecting it to avoid memset (didn't see why
>> it should), but it didn't recursively call it.  It did however, do a
>> very interesting loop unroll:
>> [...]
> What if you replace the loop with:
>    Memory := (others => Value);

That's when the generated code calls memset(3). Unless, I guess, you've
set System up to forbid composite assignments?

I changed my (Cortex) system.ads to

   Support_Aggregates        : constant Boolean := False;

and this code

      --  Initialize BSS in SRAM
      Bss := (others => 0);

results in

startup.adb:113:14: aggregate not supported by configuration

whereas system.ads:

   Support_Composite_Assign  : constant Boolean := False;

results in

startup.adb:113:11: composite assignment not supported by configuration