public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Guillaume <guillaume.thouvenin@polymtl.ca>
To: <gcc@gcc.gnu.org>
Subject: fdump-ast-original and strg:
Date: Thu, 22 Nov 2001 13:14:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33L2.0111292132350.2377-100000@leffetriple.localdomain> (raw)

Hello,

I'm student and I'm trying to build a tool which use the ASG given by g++
using the option -fdump-ast-original. Actually I build a basic parser
which reads the file file.c.original and stores the ASG in memory in a
hash table where the key is the number of a node. I also build a visitor
which visits the ASG in memory and extracts a CFG for some analysis.

The problem is the following. If you have something like:

-- part of a C code --

fprintf(stderr, "error strg: toto");

--

The asg given by gcc gives the following line:

@247    string_cst       type: @268    strg: error strg: toto  lngt: 5

So, I add a very basic modification inside GCC (in c-dump.c) and now, it
produces this line:

@247    string_cst       type: @268    strg: "error strg: toto"  lngt: 5

It is easier to parse. So, I'd like to know if it can be added to official
gcc futur release. It's only one line and for me it will be easier because
people won't need to recompile the gcc compiler if they want to use my
tool (ok for now I'm the only one who use it but it can change...).

Thank you
Sorry for my english

---
Guillaume Thouvenin
GASTA: Gcc Abstract Syntax Tree
http://gasta.sf.net





WARNING: multiple messages have this Message-ID
From: Guillaume <guillaume.thouvenin@polymtl.ca>
To: <gcc@gcc.gnu.org>
Subject: fdump-ast-original and strg:
Date: Thu, 29 Nov 2001 18:46:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33L2.0111292132350.2377-100000@leffetriple.localdomain> (raw)
Message-ID: <20011129184600.6Z2UehAlqT_CrZicT72Tmj9-M8MLnQJpSM_0BBlnQaM@z> (raw)

Hello,

I'm student and I'm trying to build a tool which use the ASG given by g++
using the option -fdump-ast-original. Actually I build a basic parser
which reads the file file.c.original and stores the ASG in memory in a
hash table where the key is the number of a node. I also build a visitor
which visits the ASG in memory and extracts a CFG for some analysis.

The problem is the following. If you have something like:

-- part of a C code --

fprintf(stderr, "error strg: toto");

--

The asg given by gcc gives the following line:

@247    string_cst       type: @268    strg: error strg: toto  lngt: 5

So, I add a very basic modification inside GCC (in c-dump.c) and now, it
produces this line:

@247    string_cst       type: @268    strg: "error strg: toto"  lngt: 5

It is easier to parse. So, I'd like to know if it can be added to official
gcc futur release. It's only one line and for me it will be easier because
people won't need to recompile the gcc compiler if they want to use my
tool (ok for now I'm the only one who use it but it can change...).

Thank you
Sorry for my english

---
Guillaume Thouvenin
GASTA: Gcc Abstract Syntax Tree
http://gasta.sf.net





             reply	other threads:[~2001-11-30  2:46 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-22 13:14 Guillaume [this message]
2001-11-22 13:14 ` Joe Buck
2001-11-23  8:49   ` Guillaume
2001-11-23  8:52     ` Florian Krohm
2001-11-23 10:56       ` Joe Buck
2001-11-30 10:22         ` Joe Buck
2001-11-23 11:04       ` Dale Johannesen
2001-11-23 16:20         ` TImode ?inhibited? in main 3.1 branch davide.rossetti
2001-11-30 12:31           ` davide.rossetti
2001-11-23 17:46         ` fdump-ast-original and strg: Tim Hollebeek
2001-11-23 18:26           ` Dale Johannesen
2001-11-30 15:02             ` Dale Johannesen
2001-11-30 14:59           ` Tim Hollebeek
2001-11-30 10:24         ` Dale Johannesen
2001-11-23 11:14       ` Zack Weinberg
2001-11-23 14:13         ` Florian Krohm
2001-11-23 14:42           ` Joe Buck
2001-11-23 23:16             ` Richard Henderson
2001-11-24  3:30               ` Zack Weinberg
2001-11-24  3:38                 ` Richard Henderson
2001-11-30 15:50                   ` Richard Henderson
2001-11-30 15:37                 ` Zack Weinberg
2001-11-30 15:28               ` Richard Henderson
2001-11-30 11:01             ` Joe Buck
2001-11-30 10:54           ` Florian Krohm
2001-11-23 16:40         ` Guillaume
2001-11-30 13:55           ` Guillaume
2001-11-30 10:26         ` Zack Weinberg
2001-11-30 10:12       ` Florian Krohm
2001-11-30  9:54     ` Guillaume
2001-11-29 19:00   ` Joe Buck
2001-11-29 18:46 ` Guillaume
2001-11-24 11:14 mike stump
2001-11-24 12:41 ` Joe Buck
2001-11-30 17:12   ` Joe Buck
2001-11-30 16:59 ` mike stump
2001-11-24 14:37 mike stump
2001-11-24 17:15 ` Joseph S. Myers
2001-11-30 18:35   ` Joseph S. Myers
2001-12-03 14:23   ` Richard Henderson
2001-11-30 17:49 ` mike stump

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.33L2.0111292132350.2377-100000@leffetriple.localdomain \
    --to=guillaume.thouvenin@polymtl.ca \
    --cc=gcc@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).