On 14/09/2021 20:48, Rafał Pietrak wrote:
W dniu 13.09.2021 o 13:41, David Brown pisze:
On 13/09/2021 11:51, Rafał Pietrak via Gcc wrote:
Hi,
Thenk you for very prompt reply.
(I'm not sure how much this is a "gcc development list" matter, rather
than perhaps a "gcc help list" or perhaps
W dniu 13.09.2021 o 13:41, David Brown pisze:
> On 13/09/2021 11:51, Rafał Pietrak via Gcc wrote:
>> Hi,
>>
>> Thenk you for very prompt reply.
>
>
> (I'm not sure how much this is a "gcc development list" matter, rather
> than perhaps a "gcc help list" or perhaps comp.arch.embedded Usenet
> g
On 13/09/2021 11:51, Rafał Pietrak via Gcc wrote:
> Hi,
>
> Thenk you for very prompt reply.
(I'm not sure how much this is a "gcc development list" matter, rather
than perhaps a "gcc help list" or perhaps comp.arch.embedded Usenet
group discussion, but I'll continue here until Jonathan or other
Hi,
Thenk you for very prompt reply.
W dniu 13.09.2021 o 10:44, Jonathan Wakely pisze:
> On Mon, 13 Sept 2021 at 07:55, Rafał Pietrak via Gcc wrote:
[-]
>> #elif VARIANT_WORKING
>> struct cr_s a = (struct cr_s) {
>> .re = 1,
>>
On Mon, 13 Sept 2021 at 07:55, Rafał Pietrak via Gcc wrote:
>
> Hi everybody,
>
> I've been using GCC for a varety of ARM micro controller project. With
> embedded systems, one often has to access specific memory locations,
> which contain hardware registers, that control device behavior.
> "tradi
Hi everybody,
I've been using GCC for a varety of ARM micro controller project. With
embedded systems, one often has to access specific memory locations,
which contain hardware registers, that control device behavior.
"traditionally" or "commonly" that's codded by programmers using
"#define", thus
