From: "Rafał Pietrak" <embedded@ztk-rp.eu>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: waffl3x <waffl3x@protonmail.com>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: wishlist: support for shorter pointers
Date: Wed, 28 Jun 2023 10:35:32 +0200 [thread overview]
Message-ID: <21650b1b-1d2e-7929-3105-b8aaca629272@ztk-rp.eu> (raw)
In-Reply-To: <CAH6eHdSLLEeTWAFM5dm4nAz3WQ+afys2FSoRYf89DTRFqf3DRQ@mail.gmail.com>
Hi Jonathan,
W dniu 28.06.2023 o 09:31, Jonathan Wakely pisze:
>
>
> On Wed, 28 Jun 2023, 08:14 Rafał Pietrak via Gcc, <gcc@gcc.gnu.org
[---------]
> 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.
>
>
> If you use a C++ library type for your pointers the syntax above doesn't
> need to change, and the fancy pointer type can be implemented portable,
> with customisation for targets where you could use 16 bits for the pointers.
As you can expect from the problem I've stated - I don't know C++, so
I'll need some more advice there.
But, before I dive into learning C++ (forgive the naive question)....
isn't it so, that C++ comes with a heavy runtime? One that will bloat my
tiny project? Or the bloat comes only when one uses particular
elaborated class/inheritance scenarios, and this particular case ( for
(...; ...; x = x->next) {} ) will not draw any of that into this project?
Not knowing C++ and wanting to check your suggestion (before I start
putting time into learning it), can you pls provide me a sample of code,
that would replace the following:
----------------
struct test_s {
struct test_s *next;
char buff[1];
};
int test_funct(struct test_s *head, char *opt) {
struct test_s *x = head;
for (; x; x = x->next) {
if (!*x->buff) { *x->buff = *opt; break; }
}
return x;
}
-----------------
.... and help me compile it into a variant with "normal/natural to
architecture" pointers, and a variant with "fancy 16-bit" pointers?
Thenx in advance,
-R
PS: as before - I don't get mails from the list, pls CC responses to me.
next prev parent reply other threads:[~2023-06-28 8:39 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
2023-06-28 7:31 ` Jonathan Wakely
2023-06-28 8:35 ` Rafał Pietrak [this message]
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=21650b1b-1d2e-7929-3105-b8aaca629272@ztk-rp.eu \
--to=embedded@ztk-rp.eu \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--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).