From: "la deng" <ladeng.mimi@gmail.com>
To: "Jan Engelhardt" <jengelh@linux01.gwdg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: c 's OOP in VFS vs c++'s OOP
Date: Sat, 5 May 2007 14:37:39 +0800 [thread overview]
Message-ID: <99e4df080705042337y7a79b321j3e5e23d83aa15b03@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0705041613580.18504@yvahk01.tjqt.qr>
On 5/4/07, Jan Engelhardt <jengelh@linux01.gwdg.de> wrote:
>
> On May 4 2007 21:53, la deng wrote:
> >>
> >> C gives you the power to control nearly everything. You can, of course,
> >> control the registers via inserting assembly code. That's not the fault of
> >> C.
> > I think you don't understand me correctly
> >
> > I know c can inline assmebly to control registers
> >
> > but,this control not the globe Analysis of control register like
> > internal of c++ compiler or lisp 's compiler language,c can't
>
> Using __asm__ in C++ is the same thing as in C. If you want to
> make GCC aware of registers you could use
>
>
> register int *p1 asm ("r0") = ...;
>
> See chapter "5.37 Variables in Specified Registers" in `info gcc`.
>
>
> Jan
> --
>
hmm,thanks
I found gcc has some extensions can help this
very thanks
next prev parent reply other threads:[~2007-05-05 6:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 8:32 la deng
[not found] ` <20070504101129.GA5482@localhost.localdomain>
2007-05-04 11:00 ` la deng
2007-05-04 11:40 ` Jan Engelhardt
2007-05-04 12:30 ` WANG Cong
2007-05-04 13:53 ` la deng
2007-05-04 14:15 ` Jan Engelhardt
2007-05-05 6:37 ` la deng [this message]
2007-05-04 15:27 ` WANG Cong
2007-05-05 7:29 ` la deng
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=99e4df080705042337y7a79b321j3e5e23d83aa15b03@mail.gmail.com \
--to=ladeng.mimi@gmail.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®