Vi presento CreaSo, semplicemente un'interfaccia che intende agevolare la procedura di creazione delle "Librerie condivise" .so (Shared Library), da utilizzare come librerie esterne in Gambas con la funzione Extern.


Gli utenti iscritti a questo forum possono scaricare la versione 0.0.6 del sorgente in fondo ⬇ nell'ultimo messaggio.

http://www.repubblica.it/motori/attualita/2012/06/07/news/arriva_l_auto_ad_aria-36653710/?ref=HRESS-7

http://www.repubblica.it/tecnologia/2012/05/28/foto/virtus_pi_veloce_del_bluetooth-35926636/1/?ref=HRESS-20   

Ambasciata della Comunità italiana di Gambas sulla mailing list internazionale

Comunicazione n. 6 dal vostro Ambasciatore    

Questa Ambasciata porta a conoscenza un avviso inviato oggi da Emil Lenngren (della mailing list internazionale di Gambas):


Hi everybody.

I've been working on a JIT-compiler for Gambas for some months, and I'm now
ready to release an alpha-version in the latest svn of Gambas.
The compiler uses LLVM to produce machine code for x86 or x86_64. You need
LLVM on your computer for it to work, preferably the latest version from
svn (3.0 from Ubuntu repos does not seem to work any well). Find more
instructions in the README file.

To use it, place the word "Fast" at the top of a Gambas Class file, for a
class that you want all functions JIT-compiled instead of interpreted. (At
the moment you cannot make individual functions JIT-compiled, but that is
limited by the gbc compiler.)

As it takes some milliseconds for LLVM to emit machine code and do
optimizations, you should only use it for functions you really need
optimizations.

As the JIT compiler analyses the whole function before execution starts,
some extra type safety is added. In interpreter mode, you can normally do
things like:
Print "hello"
Print 1.3 \ 5
and you will first see hello on the screen, and then an error message
complaining you can't do integer division on floats.
If you run the same function in the JIT compiler, the error message will be
thrown before execution starts instead, hopefully in order to make programs
less buggier.
As a consequence, you can not have code like "Try Print 1.3 \ 5" either. At
the moment the incorrect line is reported in the error message...

The best speed-ups will be in functions that use a lot of low-level
calculations and control flows (except For Each loops), like functions that
do a lot of math. If the function mostly calls other libraries, you won't
see speed-ups either.
There are still the same overhead when calling functions, since the gambas
stack must be maintained as before, to make error handling work.
Using Try/Catch is probably slightly slower too because a real exception
handler must be set up.

Something the LLVM optimizer is very good at is transforming a chain of
if-else statements to a jump table, so code like:
Select Case x
  Case 1:
    ..
  Case 2:
    ..
  Case 3:
    ..
End Select
will be much faster than before, so you don't have to use the "On Goto"
syntax and a lot of labels. This will produce identical machine code.

Most things are implemented, but there are still many bugs to fix.
Some of the (so far) unimplemented features are
Calling external C libraries (the Extern keyword).
The use of "_unknown" special method.
IIf and Choose with different argument data types.
The possibility to use Component.Load to load functions that are executed
right after in the same function.
Profiling
Breakpoints

Some of the benchmarks from http://gambasdoc.org/help/doc/benchmark
Polynom: 102.7 seconds to 4.7 seconds
Primes: 18.3 seconds to 3.5 seconds
Nbody: 16.0 seconds to 1.8 seconds

If you are curious and want to see the optimized LLVM IR you can uncomment
the line M->dump() at the bottom of the jit_codegen.cpp file in gb.jit/src.

I hope the JIT compiler will be useful for you

/Emil

Forgot to mention that the 64-bit version is probably more bug-free than
the 32-bit version, since I myself have a 64-bit computer and therefore
have run only some few tests on 32-bit...

Ambasciata della Comunità italiana di Gambas sulla mailing list internazionale

Comunicazione n. 5 dal vostro Ambasciatore     

Questa Ambasciata porta a conoscenza un avviso inviato oggi da Minisini:


Hi,

I have just added the ability to profile a project from the IDE.

This is not finished yet. At the moment, the IDE will tell you how much
time you spend in each function, and, for each function, how much time
is spent in other functions called from it.

Next, I will try to profile each line of code.

I hope it will help to optimize your projects!

Regards,

--
Benoît Minisini

Vi presento questo nuovo applicativo: Clalsa, che consente di vedere tutti i Client Midi di Alsa e le loro Porte al momento attivi ed individuarne il relativo numero identificativo.

Anche questa capacità è ottenuta utilizzando le API di Alsa mediante la funzione Extern.

Gli utenti iscritti a questo forum possono scaricare la versione 0.0.3 del sorgente qui allegato .

Io effettuo gli aggiornamenti del mio Gambas 3 tramite SVN.

Bene, da qualche mese durante la solita procedura di aggiornamento, dopo aver lanciato in terminale l'istruzione: ~/trunk $ ./configure -C, io ho ricevuto sempre questo avviso:


||
|| GNU Scientific Library component is disabled
|| GSL BLAS is disabled
||



ed alla fine ho sempre ricevuto questo messaggio
> ||
|| THESE COMPONENTS ARE DISABLED:
|| - gb.gsl


Da un po' di giorni il messaggio ha aggiunto questo nuovo componente all'avviso:

||
|| GStreamer media is disabled
||


e al termine di quella procedura ho questo avviso:

||
|| THESE COMPONENTS ARE DISABLED:
|| - gb.gsl
|| - gb.media
||


Ho posto la questione a Minisini, il quale mi ha risposto così:
« These are new components, so you must install the corresponding
development packages to compile them. »


Bene... la domanda che vorrei porvi è questa: dove trovo questi corrispondenti pacchetti ?

Quale istruzione per pulire la coda di un evento (ad esempio un _Enter() o un _MouseDown()) ?