On 11/9/18 9:58 PM, Daniel Engel wrote:
> Is the linker aware of section hierarchy, such that using a common section
> prefix (e.g. ".text.m0fp.*") would gather the appropriate sections together
> from multiple object files?
The linker script is not written like that. But we could reasonably re
Hi Richard,
I've only used custom linker scripts with my embedded work, so I don't know
much about the GCC default.
Presently, every library function is already in its own section to facilitate
--gc-sections optimization. However, I #include every file together to ensure
that all of the se
On 11/7/18 6:10 PM, Daniel Engel wrote:
> Also, loss of control of linking order would require all short branches in
> the libm section to be replaced with long branches. This particularly
> impacts the exception handling in almost every function.
You could partially remedy this by placing all
On Tue, Nov 6, 2018, at 9:28 PM, Joel Sherrill wrote:
>
> On Tue, Nov 6, 2018, 10:32 PM Daniel Engel > Hi,
>>
>> Over the past couple of years, I have hand-assembled a new floating point
>> library for the ARM Cortex M0 architecture. I know the M0 is not generally
>> regarded as a number-cr
On Tue, Nov 6, 2018, 10:32 PM Daniel Engel Hi,
>
> Over the past couple of years, I have hand-assembled a new floating point
> library for the ARM Cortex M0 architecture. I know the M0 is not generally
> regarded as a number-crunching machine, but I felt it deserved at least
> some of the attenti
Hi,
Over the past couple of years, I have hand-assembled a new floating point
library for the ARM Cortex M0 architecture. I know the M0 is not generally
regarded as a number-crunching machine, but I felt it deserved at least some of
the attention that has previously been bestowed on the AVR a
