On Mon, 27 Mar 2023 at 14:06, Steffen Möller wrote:
> Would this be something that we could address together with
> https://github.com/features/copilot?
I don't know if it would help, being trained on other code might not help
here, I doubt that what we do is at all common.
An example, see
Would this be something that we could address together with
https://github.com/features/copilot?
> Gesendet: Montag, 27. März 2023 um 10:17 Uhr
> Von: "andy pugh"
> An: "Sebastian Kuzminsky"
> Cc: "EMC developers"
> Betreff: Re: [Emc-
On Mon, 27 Mar 2023 at 04:53, Sebastian Kuzminsky wrote:
>
> I'd prefer if we used hal memory for things that need to be in hal, and
> used non-hal memory for everything else.
>
> But I don't intend to clean up all the violations of this preference, so
> my opinion doesn't count for much.
I
mån 2023-03-27 klockan 00:26 +0100 skrev andy pugh:
> I am working on a HAL driver at the moment, and have started to be
> concerned about mis-use(?) of hal_malloc.
>
> Looking at the hostmot2 code the data structures are carefully split
> into
> HAL pins and other data. The HAL pins parts are
On March 26, 2023 5:26:29 PM MDT, andy pugh wrote:
>It's a tempting thing to do, it keeps the data structures neat, and means
>that you don't have to free on exit, as the whole HAL memory is freed on
>exit.
Non-hal memory (eg from malloc) is also freed when the process exits (it's more
I am working on a HAL driver at the moment, and have started to be
concerned about mis-use(?) of hal_malloc.
Looking at the hostmot2 code the data structures are carefully split into
HAL pins and other data. The HAL pins parts are hal_malloc-ed and the data
parts are rtapi_kmalloc-ed (which is