From: "Vikas Kumar" <walburn@gmail.com>
To: Jody <jbruchon@nc.rr.com>
Cc: ELKS <linux-8086@vger.kernel.org>
Subject: Re: Ping!
Date: Mon, 5 Jun 2006 22:30:40 -0400 [thread overview]
Message-ID: <792c60620606051930k776e61e8m4ca6ef99f8707b09@mail.gmail.com> (raw)
In-Reply-To: <448458C5.1080400@nc.rr.com>
I had a question. What is the advantage of using bcc over gcc. Why is
bcc being used in some parts of the code vs gcc in other parts of the
code. A large part of the code where bcc is used to compile uses a lot
of assembly, rather than C. Why was it written this way ? Any pointers
?
Vikas
On 6/5/06, Jody <jbruchon@nc.rr.com> wrote:
> Has anyone been doing any programming on ELKS as of late?
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2006-06-06 2:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 16:16 Ping! Jody
2006-06-06 2:30 ` Vikas Kumar [this message]
2006-06-06 4:44 ` Ping! Jody
2006-06-06 9:33 ` Ping! Alan Cox
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=792c60620606051930k776e61e8m4ca6ef99f8707b09@mail.gmail.com \
--to=walburn@gmail.com \
--cc=jbruchon@nc.rr.com \
--cc=linux-8086@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