linux-kernel - Re: c 's OOP in VFS vs c++'s OOP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.61.0705041613580.18504@yvahk01.tjqt.qr>
Date:	Fri, 4 May 2007 16:15:28 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	la deng <ladeng.mimi@...il.com>
cc:	WANG Cong <xiyou.wangcong@...il.com>,
	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: c 's OOP in VFS vs c++'s OOP


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
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/