RISC-V/HiFive memory limitations
Joel Sherrill
joel at rtems.org
Fri Jun 23 14:39:28 UTC 2017
On Jun 23, 2017 9:29 AM, "Gedare Bloom" <gedare at rtems.org> wrote:
On Thu, Jun 22, 2017 at 8:32 PM, Denis Obrezkov <denisobrezkov at gmail.com>
wrote:
>> Ok, then I will try to adapt the default linkcmd file today.
>>
>> --
>> Regards, Denis Obrezkov
>
>
> Hello all,
> It seems that data section wasn't copied from ROM, so I've added the
> initialization code
> and now I have a proper value. Thus, I can proceed further to new errors.
>
> I haven't started to develop new linkcmd file, general for the
architecture
> + specific
> for the BSP. Should I? Hesham?
>
You may want to just get it working first, and then refactor the linkcmds.
+1 just make sure it is working when you start doing this. :)
> Also, I have a question:
> there is a section called 'rwbarrier' and it is placed in data. Should it
be
> also initialized?
> (copied from rom)
Everything up to the bss probably should be copied from ROM.
Agreed. Is there a crt0 in libgloss for this architecture to check against?
Just remember that the order and layout of sections may have implicit ties
to the code in the startup.
> And is it possible to decrease a required memory amount by restricting a
> user to C language usage?
> (no C++ sections in linkcmd)
>
I don't think so. They shouldn't really be having an impact anyway
except for C++ applications.
All you end up with is a loop to iterate over the list of empty global
constructors.
>
> --
> Regards, Denis Obrezkov
>
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20170623/a348585d/attachment-0002.html>
More information about the devel
mailing list