This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Newlib][libgloss]ARM - semihosting use of __end__symbol in crt0.S


Hi Tamar - Perhaps as you are working on ARM crt0 and semihosting, you can help
with a question regarding crt0's use of the symbol __end__ for semihosting.
I read the code but I'm not expert at ARM assembly and do not understand
what __end__ is being used for, and the comments do not explain the
intent/purpose...

I am concerned that there is an assumption within semihosting about available
memory or memory boundaries that may be incorrect in systems where heap
and stack are not contiguous, for example embedded systems with multiple stacks.

I asked the question on stack exchange but (surprise) didn't get any useful response:
https://stackoverflow.com/questions/44853442/meaning-of-gnu-symbol-end-especially-arm-embedded

Thanks in advance for any clarification,
Best Regards, Dave


On 7/5/2017 4:44 AM, Tamar Christina wrote:
Hi Corinna,

Ah sure, I will resend them today.

Thanks,
Tamar
________________________________________
From:newlib-owner@sourceware.org  <newlib-owner@sourceware.org>  on behalf of Corinna Vinschen<vinschen@redhat.com>
Sent: Wednesday, July 5, 2017 9:36:21 AM
To:newlib@sourceware.org
Subject: Re: [PATCH][Newlib][libgloss] - Semihosting v2 general build changes (1 / 5)

Hi Tamar,

On Jul  3 16:53, Tamar Christina wrote:
Hi All,


This patch adds the general build system changes needed
in order to compile and create the new libraries for Semihosting v2.

This works by creating a similar recursive make target that is modeled
after the existing multilib makefile config-ml.in.

OK for master?

PS. I do not have commit rights so if OK can someone apply for me?

Thanks,
Tamar


libgloss/
2017-07-03  Tamar Christina<tamar.christina@arm.com>

       * multi-build.in (multi-do): New.
We don't use ChangeLog format anymore.  Rather we would prefer
informative git commit messages and patches in `git format-patch'
format.

These 5 patches qualify as patch series, so it would be nice if
you could resend them that way.


Thanks,
Corinna

--
Corinna Vinschen
Cygwin Maintainer
Red Hat


--
Dave Nadler, USA East Coast voice (978) 263-0097,drn@nadler.com, Skype
 Dave.Nadler1


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]