[PATCH 03/52] libbsp/v850/shared/crt1.c: Remove warnings
Joel Sherrill
joel.sherrill at oarcorp.com
Wed Oct 8 20:13:27 UTC 2014
On 10/8/2014 3:06 PM, Gedare Bloom wrote:
> On Wed, Oct 8, 2014 at 3:15 PM, Joel Sherrill <joel.sherrill at oarcorp.com> wrote:
>> ---
>> c/src/lib/libbsp/v850/shared/crt1.c | 16 ++++++++++------
>> 1 file changed, 10 insertions(+), 6 deletions(-)
>>
>> diff --git a/c/src/lib/libbsp/v850/shared/crt1.c b/c/src/lib/libbsp/v850/shared/crt1.c
>> index 18c240b..02a8a7f 100644
>> --- a/c/src/lib/libbsp/v850/shared/crt1.c
>> +++ b/c/src/lib/libbsp/v850/shared/crt1.c
>> @@ -1,21 +1,25 @@
>> /*
>> * From newlib ==> libc/sys/sysnecv850/crt1.c
>> *
>> - * Obtained newlib 29 May 2012
>> + * Obtained from newlib: 29 May 2012
>> + * Warnings fixed: 7 October 2014
>> */
> Is this still from newlib? If so, should it be fixed there and re-copied over?
It originated there. That directory is not part of the v850-rtems build
because we only get the sys/rtems directory. The other sys/ directories
often contain necessary bits in the wrong place for historical reasons.
The warnings are just because we compile with pickier warnings.
I suppose we could feed this back upstream but we would still have
a copy. :)
>> -void __main ()
>> +
>> +void __main(void);
>> +typedef void (*pfunc) (void);
>> +extern pfunc __ctors[];
>> +extern pfunc __ctors_end[];
>> +
>> +void __main(void)
>> {
>> static int initialized;
>> if (! initialized)
>> {
>> - typedef void (*pfunc) ();
>> - extern pfunc __ctors[];
>> - extern pfunc __ctors_end[];
>> pfunc *p;
>>
>> initialized = 1;
>> for (p = __ctors_end; p > __ctors; )
>> - (*--p) ();
>> + (*--p) ();
>>
>> }
>> }
>> --
>> 1.9.3
>>
>> _______________________________________________
>> devel mailing list
>> devel at rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
--
Joel Sherrill, Ph.D. Director of Research & Development
joel.sherrill at OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
More information about the devel
mailing list