From: Maciej Sobczak <see.my.homepage@gmail.com>
Subject: Re: for X'Address use - and Volatile
Date: Thu, 1 Sep 2016 07:24:34 -0700 (PDT)
Date: 2016-09-01T07:24:34-07:00 [thread overview]
Message-ID: <354aaa02-2265-40e1-8e48-88036e07fc46@googlegroups.com> (raw)
In-Reply-To: <lyoa48goss.fsf@pushface.org>
> And I'd disagree with that. By the time you have
>
> * many registers to be described to the bit level
> * many peripherals in your SOC
> * more than a couple of teams involved
> * a need to handle interrupts at the Ada level (i.e. with POs)
>
> a linker script is *not* the best place to specify addresses.
Why?
In what way are the "many"'s above more difficult in the linker script than in the Ada code? Linker scripts are source files and they can be managed like other source files.
The difference is - the linker script can deal not only with the registers, but with general memory mapping for everything - including program code, stack space, free store, etc. Doing only some of it in Ada and some of it outside of it is just inconsistent. I prefer to have a consistent approach for what I consider to be a single, although general, problem (mapping of program entities to hardware).
--
Maciej Sobczak * http://www.inspirel.com
next prev parent reply other threads:[~2016-09-01 14:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 13:01 for X'Address use - and Volatile Maciej Sobczak
2016-08-31 14:00 ` AdaMagica
2016-08-31 19:36 ` Randy Brukardt
2016-08-31 22:17 ` Maciej Sobczak
2016-09-01 1:22 ` Randy Brukardt
2016-09-01 5:41 ` Simon Wright
2016-09-01 14:24 ` Maciej Sobczak [this message]
2016-09-01 8:12 ` J-P. Rosen
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox