Re: [PATCH v1 0/3 CHIP: Support vendor script libraries

[Jan Beulich <jbeulich@suse.com>]

On 15.03.2023 21:03, Ulf Samuelsson via Binutils wrote:
> On 2023-03-15 17:27, Michael Matz wrote:
>> On Tue, 14 Mar 2023, Ulf Samuelsson via Binutils wrote:
>>
>>> Introduce the CHIP command for non-MRI script files.
>>>
>>> The motivation is that you want to simplify supporting microcontrollers.
>>> You want include files that define the addresses for all peripherals
>>> and the memory/bank organisation.
>> Makes sense, but why is it not enough to use "INCLUDE(<chip>.inc)" in the
>> linker script and passing -L$LD_VENDOR_DIR/<chip> on the linker command
>> line?
> 
> Because it is a poor user interface.

That's certainly a matter of taste.

> You have to pass
> 
> -L$PROJ_DIR/<chip>
> 
> -L$LD_USER_DIR/<chip>
> 
> -L$LD_VENDOR_DIR/<chip>
> 
> to the linker every  time you link, and since most user would link with GCC
> you would have to make it more complex since you
> have to pass these things the linker through gcc.

How does gcc make it any different? It's still all the same -L options,
isn't it? You shouldn't need any -Wl,... afaict.

> so your suggestion is a lot more verbose.
> 
> I want to do
> 
> arm-none-gcc  myapp.c
> 
> and be done with it (assuming gcc will find the right linker script).
> 
> Why program in C, when you can program in assembler?

Interesting to see such a view nowadays; most projects strive to reduce
the amount of assembly code they have to maintain, afaik.

Jan