Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Martin Storsjö via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: "Martin Storsjö" <martin@martin.st>
Subject: [FFmpeg-devel] [GASPP PATCH] Translate .inst into DCD, the same as for .int or .word
Date: Wed, 12 Nov 2025 23:20:23 +0200
Message-ID: <20251112212026.4045172-1-martin@martin.st> (raw)

For ELF targets, the assembler keeps track of which words are
actual instructions, and which are data - and the disassembler
shows them differently depending on this. For other object file
formats, there's no difference. Thus, for armasm for targeting
COFF, we can treat this just like any regular integer.

Produce either a 16 or 32 bit value depending on whether we
are assembling thumb or arm. (In the case of aarch64, it is always
32 bit.)
---
Will push after a day or two.
---
 gas-preprocessor.pl | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/gas-preprocessor.pl b/gas-preprocessor.pl
index 85ccf24..ec1a6ec 100755
--- a/gas-preprocessor.pl
+++ b/gas-preprocessor.pl
@@ -1194,6 +1194,13 @@ sub handle_serialized_line {
     if ($as_type eq "armasm") {
         $line =~ s/\.global/EXPORT/x;
         $line =~ s/\.extern/IMPORT/x;
+        if ($thumb) {
+            # Translate .inst into a 16 bit thumb instruction word
+            $line =~ s/\.inst/dcw/x;
+        } else {
+            # Translate .inst into a full 32 bit word
+            $line =~ s/\.inst/dcd/x;
+        }
         $line =~ s/\.int/dcd/x;
         $line =~ s/\.long/dcd/x;
         $line =~ s/\.float/dcfs/x;
-- 
2.43.0

_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

             reply	other threads:[~2025-11-12 21:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-12 21:20 Martin Storsjö via ffmpeg-devel [this message]
2025-11-14  8:03 ` [FFmpeg-devel] " Martin Storsjö via ffmpeg-devel

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=20251112212026.4045172-1-martin@martin.st \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=martin@martin.st \
    /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

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git