Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Gudjon Gudjonsson

dblp:23/1268 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 1999
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 1 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Operating systems · 44% Compilers and program optimization · 44% Programming languages and type systems · 13%

Topics — the 3 heaviest of 3, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Operating systems › resource management
memory management
0.011999
Compile-time memory reuse in logic programming languages through update in place · ACM Trans. Program. Lang. Syst. 1999
Compilers and program optimization
program transformation
0.011999
Compile-time memory reuse in logic programming languages through update in place · ACM Trans. Program. Lang. Syst. 1999
Programming languages and type systems
logic programming
0.011999
Compile-time memory reuse in logic programming languages through update in place · ACM Trans. Program. Lang. Syst. 1999

Methods — techniques the papers use, named apart from their topics

reuse map · 0.0heuristic · 0.0
YearPublicationVenuePosition
1999 Compile-time memory reuse in logic programming languages through update in place
abstract
Standard implementation techniques for single-assignment languages modify a data structure without destroying the original, which may subsequently be accessed. Instead a variant structure is created by using newly allocated cells to represent the changed portion and to replace any cell that references a newly allocated cell. The rest of the original structure is shared by the variant. The effort required to leave the original uncorrupted is unnecessary when the program will never reference the original again. This effort includes allocating and initializing new cells, as well as garbage collecting replaced cells. This article specifies a transformation system that introduces update-in-place operations, making Prolog programs update recursive data structures much as an imperative program would. The article introduces the notion of a reuse map, which formalizes reallocation decisions. Because optimal memory reuse is intractable, a heuristical method is presented that performs well in practice. Small Prolog programs that manipulate recursive data structures have their speed increased up to about five times (naive recurse), not counting any speedup obtained by avoiding garbage collection. Quicksort is about three times as fast, merge-sort about one and a half, matrix transposition about twice, and Gaussian elimination is about 1.2 times as fast.
Gudjon Gudjonsson, William H. Winsborough
ACM Trans. Program. Lang. Syst.1