ChanServ changed the topic of #picolisp to: PicoLisp language | Channel Log: https://irclog.whitequark.org/picolisp/ | Check also http://www.picolisp.com for more information
orivej has joined #picolisp
<tankf33der> blow up heap session loop ended ok.
aw- has quit [Quit: Leaving.]
aw- has joined #picolisp
<aw-> Regenaxer: here?
<Regenaxer> Hi aw-
<aw-> question about (native) structs, if my C code returns a struct with '(B B B B) result specification? is that unaligned on 64-bit OS?
<Regenaxer> How do you mean "returns"?
<aw-> should i add a padding to make it 64-bits ?
<Regenaxer> You pass it in?
<aw-> yes i pass it in
<Regenaxer> as argument?
<aw-> yes
<aw-> and then i read it back with (struct)
<Regenaxer> It depends how it is allocated
<Regenaxer> malloc() aligns
<aw-> (setq P (native "@" "malloc" 'N 4))
<Regenaxer> Good
<Regenaxer> So the first address is aligned
<Regenaxer> should be
<Regenaxer> to any reasonable size I think
<aw-> i see..
<aw-> do you have an example where it's not aligned?
<aw-> i want to know how to avoid it
<Regenaxer> In mini pil I think there is code to force cell alignment on 32 bit systems
<Regenaxer> You could add a runtime check
<Regenaxer> (=0 (& P 15)) for example
<Regenaxer> But I think it is not necessary
<Regenaxer> unless you need alignment to more than 64 bits
<aw-> what about the C code? how do i check for alignment?
<Regenaxer> It is a feature of the C library
<Regenaxer> malloc() etc
<Regenaxer> how the heap is maintained
<Regenaxer> how about: man 3 posix_memalign
<aw-> oh that's a good start
<aw-> thanks
<Regenaxer> Just found it, didn't know before
<tankf33der> Regenaxer: when should I announce pil21 on media?
<Regenaxer> Good question, I think it is not ready
<Regenaxer> At least I want to port some docs
<Regenaxer> doc/ref*
<tankf33der> ok
<tankf33der> write announce to ML and i will link to it.
<Regenaxer> yes, good
<Regenaxer> I'm just trying pil21 on my old tablet
<Regenaxer> I get: ../pil21/bin/picolisp: unsupported flags DT_FLAGS_1=0x8000001
<Regenaxer> Do you have an idea what that means?
orivej has quit [Ping timeout: 260 seconds]
<Regenaxer> The Termux libs are upgraded though
<Regenaxer> ok, nevermind, seems just a warninng
<Regenaxer> I search later
beneroth_ has quit [Quit: Leaving]
beneroth has joined #picolisp
orivej has joined #picolisp
<tankf33der> i will try reimplement Makefile on ninja buildsystem. just for fun.
<Regenaxer> ok :)
aw- has quit [Quit: Leaving.]
libertas has quit [Quit: ZNC - https://znc.in]
libertas has joined #picolisp
<tankf33der> found this:
<Regenaxer> I think all those build systems are overkill for pil
<Regenaxer> Just a linear script is ok
<Regenaxer> Takes only a second anyway
<Regenaxer> No need for dependencies and "make clean" etc
<Regenaxer> I use a Makefile in pil only because people expect it
karswell_ has quit [Remote host closed the connection]
<tankf33der> eh.
<Regenaxer> For example, to make PilBox: http://ix.io/2Cds
<Regenaxer> run-through script
<Regenaxer> simple and clear
<Regenaxer> I used something similar to build pil64 for Arm
<Regenaxer> (but now I use pil21 directly)
<Regenaxer> http://ix.io/2Cdt
<Regenaxer> Much much more clear than a Makefile
karswell has joined #picolisp
<tankf33der> today's result: i dont understand any build system.
<tankf33der> so strange feeling.
<Regenaxer> Good :)
<Regenaxer> All overkill ;)
<tankf33der> i dont understand how people survives.
<Regenaxer> Why are you interested in build systems?
<Regenaxer> Sure, they are good and necessary if you want to build something like a Linux kernel
<tankf33der> just having fun, but all this is not fun.
<Regenaxer> Understand
orivej has quit [Ping timeout: 265 seconds]
emacsomancer has quit [Read error: Connection reset by peer]
emacsomancer has joined #picolisp
aw- has joined #picolisp