From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Cc: "Marc Nieper-Wißkirchen" <marc.nieper+gnu@gmail.com>
Subject: Re: How to fix code blocks?
Date: Mon, 02 Jan 2023 15:42:36 +0100 [thread overview]
Message-ID: <3373415.TQGk6oTFT5@nimes> (raw)
In-Reply-To: <CAEYrNrSVaJskvqCmrjKrov_K8n33EyTA5_zNFBv-s3x31FG-fw@mail.gmail.com>
Hi Marc,
> For purposes of dynamically calling code, I need the following layout
> of the assembled code:
>
> 0x00: 16-byte header
> 0x10: entry point #1
> 0x20: entry point #2
Happy new year. But this topic does not fit bug-gnulib. Maybe you sent it
to the wrong list?
Bruno
next prev parent reply other threads:[~2023-01-02 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 14:00 How to fix code blocks? Marc Nieper-Wißkirchen
2023-01-02 14:42 ` Bruno Haible [this message]
2023-01-02 14:46 ` Marc Nieper-Wißkirchen
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3373415.TQGk6oTFT5@nimes \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=marc.nieper+gnu@gmail.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).