Re: avoiding builtin memset

[Simon Wright <simon@pushface.org>]

Lucretia <laguest9000@googlemail.com> writes:

> On Wednesday, 26 April 2017 08:35:05 UTC+1, Simon Wright  wrote:
>> Luke A. Guest <me@me.com> writes:
>> 
>> > Shark8 <onewingedshark@> wrote:
>> >  
>> >>> You'll need to export that as the C memset function.
>> >> 
>> >> Even if you're only using it in Ada functions?
>> >
>> >
>> > Yup, GNAT expects certain functions to be present and generates calls
>> > to them. Check system.ads for mention of allowing assignment, that
>> > basically calls memcpy on assignment for objects that require a memory
>> > copy rather than a register to register copy.
>> 
>> Not quite sure this is set in system.ads: in the 6.1 sources, the only
>> reference to memset in the compiler itself is in exp_aggr.adb,
>
> See Support_Composite_Assign and the comment inside targparm.ads:
>
>    --  The assignment of composite objects other than small records and
>    --  arrays whose size is 64-bits or less and is set by an explicit
>    --  size clause may generate calls to memcpy, memmove, and bcopy.
>    --  If versions of all these routines are available, then this flag
>    --  is set to True. If any of these routines is not available, then
>    --  the flag is set False, and composite assignments are not allowed.

Oh, I was only looking in targparm.adb.