public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Rafał Pietrak" <embedded@ztk-rp.eu>
To: waffl3x <waffl3x@protonmail.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: wishlist: support for shorter pointers
Date: Wed, 28 Jun 2023 09:13:14 +0200	[thread overview]
Message-ID: <faa624f9-0a98-a2ea-5b09-6c9f082f8ce0@ztk-rp.eu> (raw)
In-Reply-To: <BG-6WAlLd8cp_GC2w90CYASLwGoOe5trDJnuDSN3pohbCm4xIq7f__j339eOawcuui9hkOPaYXfMlrLT7ODOOxYS58e1BtGlLU5fsNcD5wo=@protonmail.com>

Hi Alex!

W dniu 28.06.2023 o 03:54, waffl3x pisze:
> I want to preface this stating that I have little to no experience in compiler
> development, I am only merely just getting into it. With that said, I have messed around
> with library design a fair amount, and this seems like something that could be
> implemented in a library. It might be slightly comfier implemented on the compiler side,
> but I question how generally it could be implemented.

I thought of it a lot, and library implementation is something I'd 
rather avoid. Before I elaborate, let me put some excerpts of the code 
in question. GREP-ing the sources for "->next" (list processing) this is 
how it looks like. I have a lot of code like this scattered around:
-------------------
				y->next = NULL;
		if (our) { out->next = a;
		for (y = t->HD; y && y->next; y = y->next)
		if (y)	y->next = a;
			fit->HD = a->next;
		fit->win = a->next;
			b = a->next;
--------------------
This is from just one source file, which otherwise is "plain C". If I 
was to put it into a library that use "asm tweaked fancy pointers", a 
portable fragment of code becomes "target dedicated" - this is undesired.

To elaborate: even in (or may be "particularly" in) embedded world, one 
prefers to have as portable code (to other targets) as possible. And I 
must say, that such code fragments as quoted are scattered around my 
sources practically everywhere. If I "convert" them to a library, the 
entire project becomes "target locked", and in consequences 
"unmaintainable". Such move practically kills it.

Now, let me put the case into numbers: if I use stm32f030 instead of 
stm32f103, I may end up with just 4kB of RAM. The struct I heavily use 
here is 32bytes long, but with 16-bit "pointers" it collapses to 
16bytes. This structure pops up in many places and within a running 
system it may reach 100 instances. It's a LOT of space to fight for.

-R
PS: pls CC the response to my address (as you have done) - I'm not sure 
if I get mails from the list.

  reply	other threads:[~2023-06-28  7:13 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27 12:26 Rafał Pietrak
2023-06-28  1:54 ` waffl3x
2023-06-28  7:13   ` Rafał Pietrak [this message]
2023-06-28  7:31     ` Jonathan Wakely
2023-06-28  8:35       ` Rafał Pietrak
2023-06-28  9:56         ` waffl3x
2023-06-28 10:43           ` Rafał Pietrak
2023-06-28 12:12             ` waffl3x
2023-06-28 12:23               ` Rafał Pietrak
2023-07-03 14:52         ` David Brown
2023-07-03 16:29           ` Rafał Pietrak
2023-07-04 14:20             ` Rafał Pietrak
2023-07-04 15:13               ` David Brown
2023-07-04 16:15                 ` Rafał Pietrak
2023-06-28  7:34     ` waffl3x
2023-06-28  8:41       ` Rafał Pietrak
2023-06-28 13:00 ` Martin Uecker
2023-06-28 14:51   ` Rafał Pietrak
2023-06-28 15:44     ` Richard Earnshaw (lists)
2023-06-28 16:07       ` Martin Uecker
2023-06-28 16:49         ` Richard Earnshaw (lists)
2023-06-28 17:00           ` Martin Uecker
2023-06-28 16:48       ` Rafał Pietrak
2023-06-29  6:19       ` Rafał Pietrak
2023-07-03 15:07         ` Ian Lance Taylor
2023-07-03 16:42           ` Rafał Pietrak
2023-07-03 16:57             ` Richard Earnshaw (lists)
2023-07-03 17:34               ` Rafał Pietrak
2023-07-04 12:38             ` David Brown
2023-07-04 12:57               ` Oleg Endo
2023-07-04 14:46               ` Rafał Pietrak
2023-07-04 15:55                 ` David Brown
2023-07-04 16:20                   ` Rafał Pietrak
2023-07-04 22:57                 ` Martin Uecker
2023-07-05  5:26                   ` Rafał Pietrak
2023-07-05  7:29                     ` Martin Uecker
2023-07-05  8:05                       ` Rafał Pietrak
2023-07-05  9:11                         ` David Brown
2023-07-05  9:25                           ` Martin Uecker
2023-07-05 11:34                             ` David Brown
2023-07-05 12:01                               ` Martin Uecker
2023-07-05  9:42                           ` Rafał Pietrak
2023-07-05 11:55                             ` David Brown
2023-07-05 12:25                               ` Rafał Pietrak
2023-07-05 12:57                                 ` David Brown
2023-07-05 13:29                                   ` Rafał Pietrak
2023-07-05 14:45                                     ` David Brown
2023-07-05 16:13                                       ` Rafał Pietrak
2023-07-05 17:39                                         ` David Brown
2023-07-06  7:00                                           ` Rafał Pietrak
2023-07-06 12:53                                             ` David Brown
2023-07-05  9:29                         ` Martin Uecker
2023-07-05 10:17                           ` Rafał Pietrak
2023-07-05 10:48                             ` Martin Uecker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=faa624f9-0a98-a2ea-5b09-6c9f082f8ce0@ztk-rp.eu \
    --to=embedded@ztk-rp.eu \
    --cc=gcc@gcc.gnu.org \
    --cc=waffl3x@protonmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).