Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
L
LabComm
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Redmine
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Erik Jansson
LabComm
Commits
7810c9ee
Commit
7810c9ee
authored
11 years ago
by
Sven Gestegård Robertz
Browse files
Options
Downloads
Patches
Plain Diff
copied minor changes from my bzr branch
parent
fe7840b4
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/tech_report.tex
+5
-1
5 additions, 1 deletion
doc/tech_report.tex
with
5 additions
and
1 deletion
doc/tech_report.tex
+
5
−
1
View file @
7810c9ee
...
...
@@ -160,6 +160,7 @@ The LabComm compiler generates code for the declared samples, including marshall
demarshalling code, in the supported target languages.
The compiler itself is implemented in Java using the JastAdd~
\cite
{
jastadd
}
compiler compiler.
\pagebreak
\subsection
{
The LabComm library
}
The LabComm libraries contain functionality for the end-to-end transmission
...
...
@@ -168,6 +169,7 @@ the general encoding and decoding of samples, and the lower one deals with
the transmission of the encoded byte stream on a particular transport layer.
Thus, the LabComm communication stack looks like this:
\begin{figure}
[h!]
\begin{verbatim}
_______________________
| Application |
...
...
@@ -179,7 +181,7 @@ Thus, the LabComm communication stack looks like this:
| transport layer / OS|
+---------------------+
\end{verbatim}
\end{figure}
\subsubsection
{
LabComm actions
}
(similar to ioctl())
...
...
@@ -316,6 +318,7 @@ way of supporting the common cases is to include run-time checks for overflow in
and decoders.
\appendix
\newpage
\section
{
The LabComm language
}
\label
{
sec:LanguageGrammar
}
...
...
@@ -346,6 +349,7 @@ IntegerLiteral : Exp ::= <Value:String>;
VariableSize : Exp;
\end{verbatim}
\newpage
\section
{
The LabComm protocol
}
\label
{
sec:ProtocolGrammar
}
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment