From: "Bill McEnaney" <bill@rkirkpat.net>
To: Segher Boessenkool <segher@kernel.crashing.org>,
aparna@cse.iitb.ac.in, gcc-help@gcc.gnu.org
Subject: Re: insn
Date: Fri, 07 Mar 2008 18:50:00 -0000 [thread overview]
Message-ID: <20080307185014.EA5D37185C@saratoga.rkirkpat.net> (raw)
Why not write "inst" instead "insn?"
> > pls tell what exactly insn means.
>
> "insn" means "instruction". Inside of GCC, we talk so much about
> instructions that it is a lot easier to say "insns", just like you
> say "pls" instead of "please".
>
>
> Segher
>
>
________________________________________________________________
Please visit a saintly hero:
http://www.jakemoore.org
And a boy with a wonderful wish:
http://shaneswish.com/
next reply other threads:[~2008-03-07 18:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-07 18:50 Bill McEnaney [this message]
2008-03-07 19:02 ` insn Tom St Denis
-- strict thread matches above, loose matches on Subject: below --
2008-03-07 19:24 insn Bill McEnaney
2008-03-07 18:50 insn Bill McEnaney
2008-03-07 7:24 insn aparna
2008-03-07 18:40 ` insn Segher Boessenkool
2008-03-08 2:17 ` insn Ian Lance Taylor
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=20080307185014.EA5D37185C@saratoga.rkirkpat.net \
--to=bill@rkirkpat.net \
--cc=aparna@cse.iitb.ac.in \
--cc=gcc-help@gcc.gnu.org \
--cc=segher@kernel.crashing.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).