linux-toolchains.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Glaser <tg@debian.org>
To: Linus Torvalds <torvalds@linuxfoundation.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	x86@kernel.org, rostedt@goodmis.org,
	linux-kernel@vger.kernel.org, linux-toolchains@vger.kernel.org,
	jpoimboe@redhat.com, alexei.starovoitov@gmail.com,
	mhiramat@kernel.org
Subject: disassemblers (was Re: [PATCH 1/2] x86: Remove dynamic NOP selection)
Date: Sat, 20 Jan 2024 18:21:43 +0000 (UTC)	[thread overview]
Message-ID: <Pine.BSM.4.64L.2401201816560.29203@herc.mirbsd.org> (raw)
In-Reply-To: <Pine.BSM.4.64L.2401201711130.29203@herc.mirbsd.org>

Dixi quod…

>>Is there some sane tool that just does the sane thing and shows this as
>
>The only other disassemblers I know don’t know about ELF objects
>at all, I’m sorry to say.

I have searched through my bookmarks and found “Agner Fog’s objconv”
https://www.agner.org/optimize/#objconv which I had not yet tried as
it comes with a .exe but apparently, the included GPL source builds
on GNU/Linux (and BSD and MacOSX) as well.

Usage is: ./objconv -fgasm filename.o

This will write filename.asm ⚠ into the same directory as the .o file,
surprisingly.

It works for i386 and amd64 but not x32 (aka amd64ilp32) which is
mis-disassembled as if it were i386. Sample output fragment:

tsv_header:
        sub     rsp, 8                                  # 00E3 _ 48: 83. EC, 08
        lea     rdi, [.LC7+rip]                         # 00E7 _ 48: 8D. 3D, 00000000(rel)
        call    puts@PLT                                # 00EE _ E8, 00000000(PLT r)
        add     rsp, 8                                  # 00F3 _ 48: 83. C4, 08
        ret                                             # 00F7 _ C3

Bit irritating is it uses decimal numbers…

        sub     rsp, 232                                # 0102 _ 48: 81. EC, 000000E8

… and the way the input is separated with colon, period and comma,
but it’s legible enough.

Credits to Peter Cordes for the discovery.

bye,
//mirabilos
-- 
When he found out that the m68k port was in a pretty bad shape, he did
not, like many before him, shrug and move on; instead, he took it upon
himself to start compiling things, just so he could compile his shell.
How's that for dedication. -- Wouter, about my Debian/m68k revival

  reply	other threads:[~2024-01-20 18:22 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-12 11:32 [PATCH 0/2] x86: Remove ideal_nops[] Peter Zijlstra
2021-03-12 11:32 ` [PATCH 1/2] x86: Remove dynamic NOP selection Peter Zijlstra
2021-03-12 12:09   ` Peter Zijlstra
2021-03-12 20:36     ` Linus Torvalds
2024-01-20  6:58   ` Thorsten Glaser
2024-01-20  8:22     ` H. Peter Anvin
2024-01-20 16:53       ` Thorsten Glaser
2024-01-21 23:21         ` H. Peter Anvin
2024-01-21 23:58           ` Thorsten Glaser
2024-01-22  0:15             ` H. Peter Anvin
2024-01-22  0:56               ` Steven Rostedt
2024-01-22  1:17                 ` Thorsten Glaser
2024-01-22  2:04                   ` H. Peter Anvin
2024-01-22  2:15                 ` H. Peter Anvin
2024-01-22  2:22                   ` Steven Rostedt
2024-01-22  2:31                     ` H. Peter Anvin
2024-01-20 17:00       ` Linus Torvalds
2024-01-20 17:19         ` Thorsten Glaser
2024-01-20 18:21           ` Thorsten Glaser [this message]
2024-01-21 22:36         ` David Laight
2024-01-21 23:10           ` H. Peter Anvin
2021-03-12 11:32 ` [PATCH 2/2] objtool,x86: Use asm/nops.h Peter Zijlstra
2021-03-12 14:29 ` [PATCH 0/2] x86: Remove ideal_nops[] Sedat Dilek
2021-03-12 14:47   ` Borislav Petkov
2021-03-12 17:26     ` Steven Rostedt
2021-03-12 17:35       ` Sedat Dilek
2021-03-12 17:46         ` Borislav Petkov
2021-03-12 17:47         ` Steven Rostedt
2021-03-12 18:13           ` Sedat Dilek
2021-03-12 19:03             ` Sedat Dilek
2021-03-12 20:59 ` Borislav Petkov
     [not found]   ` <CA+icZUWSCS6vAQOXoG6nsW+Dbnogivzf+rmegCTMjz5hjE5cKQ@mail.gmail.com>
2021-03-13  8:49     ` Borislav Petkov
2021-03-13 11:23       ` Borislav Petkov
2021-03-13 12:10       ` Sedat Dilek
2021-03-13 12:15         ` Borislav Petkov
2021-03-13 12:38           ` Sedat Dilek
2021-03-13 12:49             ` Borislav Petkov
2021-03-13 12:58               ` Sedat Dilek
2021-03-13 13:29                 ` Borislav Petkov
2021-03-13 13:47                   ` Sedat Dilek
2021-03-15 17:04                     ` Sedat Dilek
2021-03-15 17:15                       ` Borislav Petkov
2021-03-15 17:19                         ` Sedat Dilek
2021-03-15 17:23                           ` Borislav Petkov
2021-03-15 18:10                       ` Peter Zijlstra
2021-03-15 18:23                         ` Sedat Dilek
2021-03-15 22:14                           ` Peter Zijlstra
2021-03-16  5:56                             ` Sedat Dilek
2021-03-27 12:08                               ` Sedat Dilek
2021-03-27 20:02                                 ` Linus Torvalds
2021-03-30 12:31                                   ` Sedat Dilek

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=Pine.BSM.4.64L.2401201816560.29203@herc.mirbsd.org \
    --to=tg@debian.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=hpa@zytor.com \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-toolchains@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linuxfoundation.org \
    --cc=x86@kernel.org \
    /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 NNTP newsgroup(s).