Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Sun 19 Aug 2018, 16:47
All times are UTC - 4
 Forum index » Off-Topic Area » Programming
Unbloated coding resources
Post new topic   Reply to topic View previous topic :: View next topic
Page 3 of 4 [47 Posts]   Goto page: Previous 1, 2, 3, 4 Next
Author Message
technosaurus


Joined: 18 May 2008
Posts: 4829
Location: Kingwood, TX

PostPosted: Wed 05 Nov 2014, 17:22    Post subject:  

vovchik wrote:
Dear guys,

I had some success recently getting void* work on 32 and 64-bit machines by changing that void to intptr_t. Anybody want to try that and report the results?

With kind regards,
vovchik
void * should cast properly to any pointer type (technically function pointers have slightly different rules though), that is why it should not be changed to simply int (instead of int* which is the same as intptr_t) because int is not always the same size as void* ... if you want an integer type that is the same size as void*, use size_t for unsigned and ptrdiff_t for signed... Even if size_t is larger than you need, it will simplify the assembly code because smaller types require a superfluous MOV{*} operation and it will be portable across 32/64 bit systems
_________________
Check out my github repositories. I may eventually get around to updating my blogspot.
Back to top
View user's profile Send private message Visit poster's website 
Ibidem

Joined: 25 May 2010
Posts: 553
Location: State of Jefferson

PostPosted: Thu 06 Nov 2014, 00:45    Post subject:  

technosaurus wrote:
vovchik wrote:
Dear guys,

I had some success recently getting void* work on 32 and 64-bit machines by changing that void to intptr_t. Anybody want to try that and report the results?

With kind regards,
vovchik
void * should cast properly to any pointer type (technically function pointers have slightly different rules though), that is why it should not be changed to simply int (instead of int* which is the same as intptr_t) because int is not always the same size as void* ... if you want an integer type that is the same size as void*, use size_t for unsigned and ptrdiff_t for signed... Even if size_t is larger than you need, it will simplify the assembly code because smaller types require a superfluous MOV{*} operation and it will be portable across 32/64 bit systems

If you're using a POSIX-like system, it's certain to follow ILP32/LP64: sizeof(int)==4; sizeof(long)==sizeof(void *);
sizeof(char)==1; sizeof(short)==2; sizeof(long long)==8; are also true on semi-recent POSIX-like systems.
Back to top
View user's profile Send private message 
vovchik


Joined: 23 Oct 2006
Posts: 1465
Location: Ukraine

PostPosted: Thu 06 Nov 2014, 02:55    Post subject:  

Dear technosaurus and Ibidem,

Thanks guys...I will experiment, since I have run into little problems with my own code running properly under 64-bit when written originally under 32-bit...and the problems seem to be related to my casting of pointers.

With kind regards,
vovchik
Back to top
View user's profile Send private message 
Ibidem

Joined: 25 May 2010
Posts: 553
Location: State of Jefferson

PostPosted: Thu 06 Nov 2014, 16:27    Post subject:  

More stuff...
Dropbear is a small ssh package; it can be built with ssh, sshd, scp, and key generator/convertor in one binary.
Uses libtom* for crypto; sqlite and wpa_supplicant can also be configured to use libtom*.

Toybox includes a dhcp client, dhcp server, syslogd/klogd, tftpd, and crond/crontab. Bootchartd, inotifyd, and telnetd might also be interesting. Haven't tested if toybox mount works right with fstab yet.

Lots of neat stuff over at litcave, especially neatroff and fbvnc.
fbvis is a tiny framebuffer image viewer (132 kb linked static against musl); supports JPEG PNG PPM TGA BMP PSD GIF(partial) HDR PIC, using lodepng, stb_image, and a builtin ppm loader.

Keys: vi keys for scrolling (hjkl), J/n for next image, K/p for previous, f for zoom to height, w is zoom to width.
See README for more.

Thinking it would be handy to have a thermald/powerd or such (monitors temperature, load, and battery; controls cpu frequency/governor and fan; can run arbitrary commands).

Is there an update for libc.h, or was 0.1 the last release?
Back to top
View user's profile Send private message 
technosaurus


Joined: 18 May 2008
Posts: 4829
Location: Kingwood, TX

PostPosted: Thu 06 Nov 2014, 20:59    Post subject:  

Yeah I like the litcave frame buffer tools as well ... Fbvis can be modified to only use stb_image with only a couple of modifications... Can't believe I didn't already mention dropbear but yeah... I wonder if we could add audio forwarding capability to dropbear? Maybe by capturing/dev/dsp and putting it on a udp or tcp socket
_________________
Check out my github repositories. I may eventually get around to updating my blogspot.
Back to top
View user's profile Send private message Visit poster's website 
Ibidem

Joined: 25 May 2010
Posts: 553
Location: State of Jefferson

PostPosted: Mon 10 Nov 2014, 19:13    Post subject:  

technosaurus wrote:
Can't believe I didn't already mention dropbear but yeah... I wonder if we could add audio forwarding capability to dropbear? Maybe by capturing/dev/dsp and putting it on a udp or tcp socket


Probably not reliably; AFAICT, that would only work for OSS3 dynamically linked stuff, we'd need to handle ioctls, etc...
(OSS4 uses a slightly different set of ioctls; Pulse and ALSA are pretty different.)

I'm still wondering whether libc.h has been upgraded since 0.1, if the string.h replacements ever happened, and what the status of all that is.
Back to top
View user's profile Send private message 
technosaurus


Joined: 18 May 2008
Posts: 4829
Location: Kingwood, TX

PostPosted: Mon 10 Nov 2014, 23:29    Post subject:  

Ibidem wrote:
technosaurus wrote:
Can't believe I didn't already mention dropbear but yeah... I wonder if we could add audio forwarding capability to dropbear? Maybe by capturing/dev/dsp and putting it on a udp or tcp socket


Probably not reliably; AFAICT, that would only work for OSS3 dynamically linked stuff, we'd need to handle ioctls, etc...
(OSS4 uses a slightly different set of ioctls; Pulse and ALSA are pretty different.)
The reason I ask, is that I am trying to figure out a way to use linux containers to allow up to 65k users to run applications on the same system. X apps can use ssh -X -C, but so far pulse audio is the only thing in use ... well, there is NAS (which I would prefer due to licensing and less general suck-ness) _but_ according to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655361, it will take some patching. ... but that is probably a topic for another thread, especially since (IMHO) this is an area where systemd can be useful and any mention of it tends to awaken all the rabble-rousers.
Ibidem wrote:
I'm still wondering whether libc.h has been upgraded since 0.1, if the string.h replacements ever happened, and what the status of all that is.
I don't know about upgraded, so much as changed. I did a lot of testing and compilers had difficulty eliminating unused code without the --*-sections flags. Adding static to the functions helped, but made programs built from multiple *.c files larger due to duplicated functions.
After a lot of experimentation I started separating each function into its own file and using an awk script to detect usage of functions and build a stripped down libc.h adding static to functions if only a single c file (main.c) is used or the function is only used once.

Part of this was also preparing for a future version where shared libraries are allowed (my current _start function does not handle shared libraries), so that we are capable of building a single shared library with only functions needed by multiple programs (others will be built in to the single program that uses it) similar to http://libraryopt.sourceforge.net/ but only requiring awk (even the busybox version) and a C toolchain. The resulting library should also be significantly smaller than the libraryopt rebuild, but with the requirement of a busybox/toybox (more like buildroot) style build system.

If having a single libc.h is desirable, I could probably add a build script or make file target to generate it.... possibly even a target to build it into the standard *.h files like string.h, stdio.h, etc... In the mean time musl-libc is what I normally use unless I am trying to squeeze an app into CPU cache.

_________________
Check out my github repositories. I may eventually get around to updating my blogspot.
Back to top
View user's profile Send private message Visit poster's website 
minux


Joined: 10 Jan 2016
Posts: 7
Location: Jakarta

PostPosted: Mon 07 Mar 2016, 18:17    Post subject:  

technosaurus wrote:


smaller alternative to tinyX
http://galos.no-ip.org/siX



Good morning ,do you have the file ?
I think galos is offline.
Back to top
View user's profile Send private message Visit poster's website 
technosaurus


Joined: 18 May 2008
Posts: 4829
Location: Kingwood, TX

PostPosted: Wed 31 Jan 2018, 19:43    Post subject:  

minux wrote:
technosaurus wrote:


smaller alternative to tinyX
http://galos.no-ip.org/siX



Good morning ,do you have the file ?
I think galos is offline.

Sorry for the late reply. The copy of siX that I had, does not include a license, so I can' repost it, but I did find some info here:
http://betteros.org/tut/graphics1.php
Its actually the best tutorial I have found on low level Linux graphics.

I've been meaning to do some experiments with replacing X11/xcb with a C99+structs based alternative - total "library" size should be minimal (<32kb) but designed for static builds as a single file header library. My initial experiments actually decreased the size of the binary because only 1 struct is created per request and no extraneous data needs to be saved between function calls (such as data saved in callee clobbered registers that would need to be pushed and popped from the stack) It was also faster because data doesn't need to be copied to a new struct for each request (nearly every X function) ... it also shrinks the code a bit too because it doesn't have to do a memcpy and because of this, allows the compiler to fully optimize and inline many functions into "leaf" functions that can also be easily be inlined (thus eliminating most of the function call overhead).

_________________
Check out my github repositories. I may eventually get around to updating my blogspot.
Back to top
View user's profile Send private message Visit poster's website 
technosaurus


Joined: 18 May 2008
Posts: 4829
Location: Kingwood, TX

PostPosted: Thu 15 Feb 2018, 20:45    Post subject:  

https://github.com/lc-soft/LCUI
_________________
Check out my github repositories. I may eventually get around to updating my blogspot.
Back to top
View user's profile Send private message Visit poster's website 
technosaurus


Joined: 18 May 2008
Posts: 4829
Location: Kingwood, TX

PostPosted: Thu 15 Feb 2018, 20:46    Post subject:  

Here are github projects to replace larger versions:
pulseaudio
systemd
logind
udev
libevent
alsa
x11
xserver
glibc over musl

_________________
Check out my github repositories. I may eventually get around to updating my blogspot.
Back to top
View user's profile Send private message Visit poster's website 
RetroTechGuy


Joined: 15 Dec 2009
Posts: 2898
Location: USA

PostPosted: Fri 20 Jul 2018, 11:34    Post subject:  

technosaurus wrote:
Here are github projects to replace larger versions:
[...]


Thanks Techno... Gonna reply just so I can "pin" this to my list... Wink

_________________
Add swapfile
WellMinded Search
Back to top
View user's profile Send private message 
musher0


Joined: 04 Jan 2009
Posts: 12578
Location: Gatineau (Qc), Canada

PostPosted: Fri 20 Jul 2018, 12:29    Post subject:  

Interesting.

But
1) how up-to-date are those projects?

2) how compatible are they with any Puppy?

3) how do you integrate them with any Puppy? One of those authors mention a
way to do a debian install of his project. That is neither fun nor funny. Sad

BFN.

_________________
musher0
~~~~~~~~~~
Siempre será canción nueva... (V. Jara, Manifiesto)
Back to top
View user's profile Send private message 
wiak

Joined: 11 Dec 2007
Posts: 934
Location: not Bulgaria

PostPosted: Sat 21 Jul 2018, 00:16    Post subject:  

musher0 wrote:

3) how do you integrate them with any Puppy? One of those authors mention a
way to do a debian install of his project. That is neither fun nor funny. Sad

BFN.


One of the good things about the DebianDogs being on Puppy forum is that they contain simple tools for extracting and creating debs. Nowadays I normally create my own packages in deb format, since it is so universal (and easy to change to dotpet format as explained next).

However, in most any DebianDog I can extract the deb (a simple filemanager right-click option) and then, once booted back into a Puppy system, run dir2pet, or similar on it, to produce a dotpet. Works fine for simple packages/programs anyway. For more complicated cases you may need to check you have all the correct package dependencies in Puppy prior to producing the dotpet, but that is usually not a difficult task.

I suspect there is a simple deb2pet package available on Pups too (though I can't remember) but sometimes it is better to extract and examine deb package first, to see if you need anything extra to make desired dotpet creation work. Of course, I realise many Pups will install debs anyway, but again success or failure may vary if the deb contents aren't extracted and checked first.

wiak
Back to top
View user's profile Send private message 
technosaurus


Joined: 18 May 2008
Posts: 4829
Location: Kingwood, TX

PostPosted: Sat 21 Jul 2018, 03:12    Post subject:  

I've been working on a next generation version of puppy for a while that will incorporate many of the lightweight libraries but I am so unsatisfied with the X and C libraries, that I got sidetracked on reimplementing those first. Both will be single header libraries designed for static builds of multi call binaries. Once those are complete, I will put together the MCB with an Xserver, window manager, terminal, editor, browser, web server (for slitaz style configuration) and a few basic utilities. Each program will be a single c file that doesn't share any function names with the others so that all compilers will be able to do whole program optimization for the entire MCB. I haven't made most of the work public yet, but check out the github repositories that I have starred to get an idea... mostly single header libraries if there is one and only permissive licenses.
_________________
Check out my github repositories. I may eventually get around to updating my blogspot.
Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 3 of 4 [47 Posts]   Goto page: Previous 1, 2, 3, 4 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Off-Topic Area » Programming
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0793s ][ Queries: 14 (0.0038s) ][ GZIP on ]