linux-kernel - Re: use of setjmp/longjmp in x86 emulator.

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]

Date:	Mon, 01 Mar 2010 15:43:53 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Zachary Amsden <zamsden@...hat.com>
CC:	Gleb Natapov <gleb@...hat.com>, linux-kernel@...r.kernel.org,
	mingo@...e.hu, avi@...hat.com, mtosatti@...hat.com
Subject: Re: use of setjmp/longjmp in x86 emulator.

On 03/01/2010 03:34 PM, Zachary Amsden wrote:
> 
> But I'd rather implement a new language where acquisition of resources 
> such as locks, dynamically allocated objects, and ref counts are 
> predicated in the function typing and are heavily encouraged to possess 
> defined inverses.  Then the closure of a particular layer of nesting 
> already has enough information to provide release upon escape, and the 
> compiler can easily take the burden of checking for a large class of 
> lock and resource violation.
> 
> And it would have to be prettier than the current languages that do 
> that, meaning operator overloading would be banned.  Although it would 
> define rational numbers, super-extended precision arithmetic, imaginary 
> numbers, quaternions and matrices as part of the spec, so there would be 
> no need to use arithmetic overrides anyway, and then all the nonsensical 
> operators could die, die, die, especially the function () and logical 
> operator overrides.
> 

/me takes away Zach's caffeine.

	-hpa

--
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/