kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: john@jjdev.com (John de la Garza)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Achieve multi-threading in MIPS assembly
Date: Tue, 21 Apr 2015 10:02:56 -0700	[thread overview]
Message-ID: <20150421170255.GB3971@sol.jjdev.com> (raw)
In-Reply-To: <9851.1429581146@turing-police.cc.vt.edu>

On Mon, Apr 20, 2015 at 09:52:26PM -0400, Valdis.Kletnieks at vt.edu wrote:
> On Tue, 21 Apr 2015 01:05:19 -0000, "Chaturvedi, Akash" said:
> 
> > I am writing MIPS assembly code for a 'Word guessing game'.
> 
> Why?
> 
> gcc -O2 will almost certainly generate faster code than you can (unless you're
> *really* good at MIPS assembler, in which case you wouldn't have posted).

This is a common response to questions like this (questions asking
about assembly language).  Learning assembly can be fun.  When I read
this question, my first thought was 'cool, someone is learning assembly
language'.  Then I wondered how this is related to the topic of this list.

I see two camps.  One says don't bother to learn assembly because a compiler
is usually better.  The other says, learning assembly language will help
you be a better programming in general.

I have always been curious about assembly language.  Taking a few months
and writing a bunch of programs in assembly then seeing how others did
it was really an overall good thing.

Assembly language seemed like magic to me for many years.

      reply	other threads:[~2015-04-21 17:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-21  1:05 Achieve multi-threading in MIPS assembly Chaturvedi, Akash
2015-04-21  1:52 ` Valdis.Kletnieks at vt.edu
2015-04-21 17:02   ` John de la Garza [this message]

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=20150421170255.GB3971@sol.jjdev.com \
    --to=john@jjdev.com \
    --cc=kernelnewbies@lists.kernelnewbies.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).