gasta-general — General discussion about gasta

[Gasta-general] FASD project: Online survey launched

[Benno L. <ben...@id...>]

Dear Open Source developer

I am doing a research project on "Fun and Software Development" in which I
kindly invite you to participate.
You will find the online survey under http://fasd.ethz.ch/qsf/. The
questionnaire consists of 53 questions and you will need about 15 minutes to
complete it.

With the FASD project (Fun and Software Development) we want to define the
motivational significance of fun when software developers decide to engage
in Open Source projects. What is special about our research project is that
a similar survey is planned with software developers in commercial firms.
This procedure allows the immediate comparison between the involved
individuals and the conditions of production of these two development
models. Thus we hope to obtain substantial new insights to the phenomenon of
Open Source Development.


With many thanks for your participation,
Benno Luthiger


PS:
The results of the survey will be published under
http://www.isu.unizh.ch/fuehrung/blprojects/FASD/.
We have set up the mailing list fa...@we... for this study. Please
see http://fasd.ethz.ch/qsf/mailinglist_de.html for registration to this
mailing list.

_______________________________________________________________________

Benno Luthiger
Swiss Federal Institute of Technology Zurich
8092 Zurich

Mail: benno.luthiger(at)id.ethz.ch
_______________________________________________________________________

[Gasta-general] version 2.1.1-pre3 is available

[<gui...@po...>]

The main improvement is the new fix point algorithm (annotAnalysis.c)
which detect if a pointer can be nul when it reaches a return statement.
It will allow the annotation of the funtion as it can return a nul
pointer /*@NULL@*/. There is still some troubles but this is the first
steps before the real annotation...

Guillaume

[Gasta-general] [Fwd: gasta-2.0.1 released]

[<gui...@po...>]

It seems that this message is not passed the first time. If you receive
it twice, sorry for the double message

----- Forwarded message from gui...@po... -----

From: gui...@po...
To: gasta-general <gas...@li...>
Subject: gasta-2.0.1 released


Hello,

 There is a new version of Gasta.
 
 We changed the major number because the code has been for the largest
part rewritten.

 The main algorithm has been removed but we are working on it and it will
be available in a week or two. We made this release because we received
many reports concerning problems about the use of gasta-1.3.1 and thus, as 
many problems are resolved by this version, we released it (even if it's not 
completed yet)

ChangLog:

- We replaced almost every pointer to a character by pointers to a
  GString.
- We added many comments and rewrote some pieces of code.
- We changed the majority of variables names
- We cleaned our builder (annotBuilder)
- We removed the analysis (add a while(0){ ... };) and we are working
  on it.
- The generation of the CFG has been tested on programs from the
  glib and textutils packages. It works. We found a little problem
  and we will correct it in the next release.

We add two new files : defaultBuilder.c and annotCode.c

Version is available at:
http://sourceforge.net/project/showfiles.php?group_id=26785

or by CVS using the TAG rel-2_0_1-final
http://gasta.sf.net

----- End forwarded message -----

[Gasta-general] gasta-2.0.1 released

[<gui...@po...>]

Hello,

 There is a new version of Gasta.
 
 We changed the major number because the code has been for the largest
part rewritten.

 The main algorithm has been removed but we are working on it and it will
be available in a week or two. We made this release because we received
many reports concerning problems about the use of gasta-1.3.1 and thus, as 
many problems are resolved by this version, we released it (even if it's not 
completed yet)

ChangLog:

- We replaced almost every pointer to a character by pointers to a
  GString.
- We added many comments and rewrote some pieces of code.
- We changed the majority of variables names
- We cleaned our builder (annotBuilder)
- We removed the analysis (add a while(0){ ... };) and we are working
  on it.
- The generation of the CFG has been tested on programs from the
  glib and textutils packages. It works. We found a little problem
  and we will correct it in the next release.

We add two new files : defaultBuilder.c and annotCode.c

Version is available at:
http://sourceforge.net/project/showfiles.php?group_id=26785

or by CVS using the TAG rel-2_0_1-final
http://gasta.sf.net

[Gasta-general] gasta first try

[<ma...@fu...>]

Okay, I installed gcc 3.0.3 and I ran g++ with -fdump-ast-original

Now, when I run gasta I get
./gasta  -t DOT -o out -i ~/hqslib/border.c.original
<BEGIN gasta-1.4.1>
Recovering options ...                  done
Open /hsgi/mathew/hqslib/border.c.original ...          done
parse error
Start parse input file ...              asgparse return 1.
Please check your input file.
Close input file ...                    done
Release the memory ...                  done
<END>


--------------------------------------------
should I send the file border.c.original?

Mathew

Re: [Gasta-general] how to dump translation unit?

[Guillaume <gui...@po...>]

On Mon, 21 Jan 2002, Mathew Yeates wrote:

> Hi

Hi Mathew,

> I'm using gcc 2.95.3 and I don't see the option to do this.
> Of all of the "dump" options, none of them produce a file
> with the extension .ast. ???

Those options are available with 2.96 versions and higher (for 2.96 I
think that there is only one option which -fdump-translation-unit and
from 3.0 they added "-fdump-ast-original and others"). The current
version release of gcc is 3.0.3 and options like "-fdump-ast-original"
are available only for g++. Here is a sample from
http://gcc.gnu.org/onlinedocs/gcc-3.0.3/gcc_3.html#SEC3 :

...
-fdump-ast-switch (C++ only)
-fdump-ast-switch-number (C++ only)
      Control the dumping at various stages of processing the abstract
syntax tree to a file. The file name is generated by appending a switch
specific suffix to the source file name. If the
      `-number' form is used, number is a bit mask which controls the
details of the dump. The following bits are meaningful (these are not set
symbolically, as the primary function of
      these dumps is for debugging gcc itself):

      `bit0 (1)'
            Print the address of each node. Usually this is not meaningful
as it changes according to the environment and source file.
      `bit1 (2)'
            Inhibit dumping of members of a scope or body of a function,
unless they are reachable by some other path.

      The following tree dumps are possible:
      `original'
            Dump before any tree based optimization, to `file.original'.
      `optimized'
            Dump after all tree based optimization, to `file.optimized'.
...

If you only use C files, unfortunatly it can be a problem. For example,
I'm trying to compile real C programs for testing and there is always
problems, especially with types of variables because C accepts more things
than C++.

Guillaume

[Gasta-general] how to dump translation unit?

[Mathew Y. <ma...@fu...>]

Hi
I'm using gcc 2.95.3 and I don't see the option to do this.
Of all of the "dump" options, none of them produce a file
with the extension .ast. ???

Mathew

[Gasta-general] gasta-1.3.1 released

[Guillaume <gui...@po...>]

This version corrects mistakes in the extraction of the CFG.
The control flow graph should be correct now.

Guillaume

[Gasta-general] State of the art

[Guillaume <gui...@po...>]

gasta-1.2.1 is a new release of gasta.
The main improvement is the extraction of the CFG. There is some points
that are missing like the treatment of the return block in the CFG. This
is done in cvs version (visitGraph.c : version 4.1).

The next step of our project is the implementation of an iterative
algorithm for reaching annotations [*]. For example, a modify expression
like :

 intPtr = (int *) malloc (sizeof(int));

 will be annotated with "NULL" and "ONLY" tags. The iterative analysis
will allow to compute the value of such pointer by holding account of the
different path inside the CFG.

Each suggestion is welcome.
Guillaume

[*] Compilers Principles, Techniques, and Tools.
    Alfred V.Aho, Ravis Sethi, Jeffrey D.Ullman
    p 625: Iterative solution of data-flow equations