linux-assembly.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Landon Blake" <lblake@ksninc.com>
To: linux-assembly@vger.kernel.org
Subject: FW: Machine Code
Date: Mon, 12 Dec 2005 11:55:06 -0800	[thread overview]
Message-ID: <0D544207876CDA428F17DD7EA448C192088C38@bailey.DOMAIN.KSNINC.PVT> (raw)



Is it possible to write machine code instruction directly to the
computers memory without using an assembler? Is there an open source
"binary file" editor that someone can recommend that will allow me to do
this?

Do chip manafacturers typically provide an assembler that compiles
assembly language instructions into the machine code for there
processor, or does a programmer have to rely on third parties for the
assemblers?

I'm just wondering if it is possible to write a machine code file
directly without the need for an assembler.

Landon


             reply	other threads:[~2005-12-12 19:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-12 19:55 Landon Blake [this message]
2005-12-12 20:17 ` FW: Machine Code Brian Raiter
2005-12-12 20:36 ` Claudio Fontana
2005-12-13  1:31 ` Ricardo Nabinger Sanchez

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=0D544207876CDA428F17DD7EA448C192088C38@bailey.DOMAIN.KSNINC.PVT \
    --to=lblake@ksninc.com \
    --cc=linux-assembly@vger.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 read-only IMAP folder(s) and NNTP newsgroup(s).