From: bzs@TheWorld.com
To: Jesse Thompson <jesset@gmail.com>
Cc: cygwin@cygwin.com
Subject: Re: Request for an example x68 assembler portable Hello World script
Date: Sat, 27 Apr 2019 18:35:00 -0000 [thread overview]
Message-ID: <23748.41133.822313.11282@gargle.gargle.HOWL> (raw)
In-Reply-To: <CA+wh7Kg+KDGN0b=-UFZ7UnX_fgHw69p_PXmdaqSrncHZsVGCbA@mail.gmail.com>
Just two thoughts:
1. You probably know that 'cc -S foo.c' produces foo.s which is the
assembler output. Might be worthwhile examining how the experts who
wrote the C compiler handle all this. The output is usually quite
readable for someone prone to reading such things.
2. Rather than generating asm some developers generate C and run that
thru the C compiler. One advantage is you can leverage all the C code
optimization and debugging etc infrastructure and anything else you
can find on the C and ld etc man pages (e.g., PIC.)
But there's nothing wrong with learning assemblers and machine
languages. In the distant past I taught it for several years at Boston
University so, good luck!
--
-Barry Shein
Software Tool & Die | bzs@TheWorld.com | http://www.TheWorld.com
Purveyors to the Trade | Voice: +1 617-STD-WRLD | 800-THE-WRLD
The World: Since 1989 | A Public Information Utility | *oo*
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-04-27 18:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 7:25 Jesse Thompson
2019-04-26 11:16 ` Eliot Moss
2019-04-26 21:04 ` Jesse Thompson
2019-04-27 1:56 ` Doug Henderson
2019-04-27 18:35 ` bzs [this message]
2019-04-28 20:00 ` Eliot Moss
2019-04-29 14:29 ` Sam Habiel
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=23748.41133.822313.11282@gargle.gargle.HOWL \
--to=bzs@theworld.com \
--cc=cygwin@cygwin.com \
--cc=jesset@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).