<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.jvmlangsummit.com/index.php?action=history&amp;feed=atom&amp;title=Fortress</id>
	<title>Fortress - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.jvmlangsummit.com/index.php?action=history&amp;feed=atom&amp;title=Fortress"/>
	<link rel="alternate" type="text/html" href="https://wiki.jvmlangsummit.com/index.php?title=Fortress&amp;action=history"/>
	<updated>2026-10-30T23:09:12Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.32.0</generator>
	<entry>
		<id>https://wiki.jvmlangsummit.com/index.php?title=Fortress&amp;diff=50&amp;oldid=prev</id>
		<title>Jrose: New page: == Fortress: running your whiteboard, on the JVM.  == David Chase, Sun  === Abstract === Fortress is a new programming language, originally intended for high- performance computing, but ge...</title>
		<link rel="alternate" type="text/html" href="https://wiki.jvmlangsummit.com/index.php?title=Fortress&amp;diff=50&amp;oldid=prev"/>
		<updated>2008-09-24T18:19:24Z</updated>

		<summary type="html">&lt;p&gt;New page: == Fortress: running your whiteboard, on the JVM.  == David Chase, Sun  === Abstract === Fortress is a new programming language, originally intended for high- performance computing, but ge...&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;== Fortress: running your whiteboard, on the JVM.  ==&lt;br /&gt;
David Chase, Sun&lt;br /&gt;
&lt;br /&gt;
=== Abstract ===&lt;br /&gt;
Fortress is a new programming language, originally intended for high-&lt;br /&gt;
performance computing, but generally applicable to the multicore world.  Our aim&lt;br /&gt;
is to allow programs expressed in a style as close to mathematical notation as&lt;br /&gt;
possible, to effectively use multicore parallelism, for large values of &amp;quot;multi&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Challenges in the mapping to the JVM include:&lt;br /&gt;
* thread model mismatch (Fortress depends on workstealing)&lt;br /&gt;
* type system mismatch (Fortress does not erase its types)&lt;br /&gt;
* dispatch mismatch (it's multiple; we think we will compile this into visitors or decision trees as appropriate)&lt;br /&gt;
* transactions (nested and executed by multiple threads)&lt;br /&gt;
* value objects (return values, in arrays)&lt;br /&gt;
* clean mapping to legacy (FORTRAN) libraries&lt;br /&gt;
* access to FP ops carried out in different rounding modes.&lt;br /&gt;
* proper tail call elimination, perhaps?&lt;br /&gt;
&lt;br /&gt;
http://wiki.jvmlangsummit.com/pdf/16_Chase_fortress.pdf&lt;br /&gt;
&lt;br /&gt;
=== Author Bio ===&lt;br /&gt;
&lt;br /&gt;
=== Key Issues for Discussion (cooperative) ===&lt;br /&gt;
''(please expand cooperatively)''&lt;br /&gt;
[[Talk:Fortress]]&lt;/div&gt;</summary>
		<author><name>Jrose</name></author>
		
	</entry>
</feed>