mono

(redirected from JIT compiler)
Also found in: Dictionary, Thesaurus, Legal, Encyclopedia.

mono

(mŏn′ō)
n. Informal
Infectious mononucleosis.
The American Heritage® Medical Dictionary Copyright © 2007, 2004 by Houghton Mifflin Company. Published by Houghton Mifflin Company. All rights reserved.

mono

 Infectious mononucleosis, see there.
McGraw-Hill Concise Dictionary of Modern Medicine. © 2002 by The McGraw-Hill Companies, Inc.

Patient discussion about mono

Q. can mono kill you if it gets to the liver? otherwise known as the kissing desiaes.

A. It can be fatal, not necessarily through infecting the liver but through rupture of enlarged spleen or obstruction of the throat, or through the development of cancer (e.g. lymphoma) later in life.

However, these complications are very rare, and most people recover from the disease without major complications.

You can read more here: http://www.nlm.nih.gov/medlineplus/infectiousmononucleosis.html

More discussions about mono
This content is provided by iMedix and is subject to iMedix Terms. The Questions and Answers are not endorsed or recommended and are made available by patients, not doctors.
References in periodicals archive ?
Most existing stack-based JIT compilers solve this problem by expending compilation effort to transform their input programs into an internal three-address code representation (often in SSA form) on which the optimizations are performed.
SafeTSA successfully augments a tree-oriented intermediate representation with instructions in SSA form, which is already used internally in several static and JIT compilers and that is considered the state-of-the-art intermediate representation for intra-procedural scalar optimizations.
In recent years program annotations have been suggested as a way to improve the code generation of JIT compilers. The term program annotation is used as a synonym for code information added to the mobile code during its generation.
These annotations carry compiler optimization-related information that allow the JIT compiler to generate optimized native code without extensive runtime analysis.
CACAO is a stand-alone JIT compiler for the DEC ALPHA architecture [Krall and Graft 1997].
Fajita [FAJITA] is a variation of a JIT compiler that runs as a Java compilation server on a network, independent of the Java runtime.
The main difference between a direct compiler and a JIT compiler is that the compiled code generated by a direct compiler is available for future executions of the Java program.
While a JIT compiler can provide significant speedups over an interpreter, it introduces additional compilation time and can require a large amount of memory.
In addition, it was designed to simplify the task of writing an interpreter or a JIT compiler for a specific target processor and operating system.
1997] executes Java applications on an ILP machine with a Java JIT compiler hidden within the chip architecture.
This on-line version of Briki is integrated with the Kaffe JIT compiler [Wilkinson, Kaffe v0.10.0], using Kaffe to generate an IR.
The Symantec Cafe JIT compiler has been shown to be about 5 times faster, on average, than the Sun JDK1.0.2 interpreter based on the Java version of the C programs cmp, grep, wc, Pi, Sieve, and compress [Hsieh et al.