public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Eric Methot <methote@videotron.ca>
To: egcs@cygnus.com
Subject: GCC Help
Date: Tue, 15 Dec 1998 10:18:00 -0000	[thread overview]
Message-ID: <000901be2854$dc324b00$320171d8@enzo.videotron.ca> (raw)

Hello everyone,

Being a beginer at building front ends, I could use a little help
or a push in the right direction.

I am trying to do the following source to source transformation
inside the C compiler ( as a new front-end of course )

fun( a, g(2), p )

becomes:

struct { void* arg0, int arg1, int arg2, int *result } __desc = { myWrapper,
a, g(2), p };

I have tried to replace the action for building function calls
in the "primary : primari '(' exprlist ')' rule but ran in to many problems.

Am I on the right track?
Perhaps someone has already done this?

Also how can I create a global declaration while parsing a function
i.e. the declaration of my wrapper functions.  It seems that the nodes
get destroyed as soon as the parsing of the function is done.

By the way, when this compiler is done it will be realeased as a new
front-end
to gcc ( GPL ) along with the accompanying library ( GPL ).

Thanks,  Eric ;-)

             reply	other threads:[~1998-12-15 10:18 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-15 10:18 Eric Methot [this message]
2000-06-13 14:09 Amir Elaguizy
2000-06-13 14:15 ` llewelly
2000-06-13 14:16 ` Mo McKinlay
2000-06-13 14:37 ` Alexandre Oliva
2000-07-21 14:35 Gcc Help Koaps
2000-07-21 14:49 ` Alexandre Oliva
2000-07-21 14:42 Anjul Srivastava
2001-10-14 22:12 GCC help pradeep kumar mishra
2001-10-15  4:49 ` Erik Mouw
2001-12-18 12:16 gcc help ashish  kamble
     [not found] <616BE6A276E3714788D2AC35C40CD18D29DB3D@whale.softwire.co.uk>
2001-12-18 23:44 ` Rupert Wood
2002-02-19  5:32 GCC help aditya nishandar
2002-02-19  8:12 ` Philipp Thomas
2002-10-25 16:21 gcc help MICHAEL GOODWIN
2003-12-03 17:48 GCC help George Ciobanu
2003-12-04 20:10 ` Jim Wilson
2004-01-22  8:22 gcc help Andrew
2004-01-22 22:06 ` Jim Wilson
2004-09-09  9:53 GCC help Sonawane Sachin Vijayku
2004-09-09 10:08 ` Sonawane Sachin Vijayku
2004-09-09 10:25 ` Ranjit Mathew
2004-09-09 10:37 ` Nathan Sidwell
2004-09-09 10:40   ` Nathan Sidwell
2005-03-29 17:54 Gcc help andre
2005-03-29 18:10 ` andre
2005-03-29 19:02 ` Eljay Love-Jensen
2005-03-29 19:15   ` Eljay Love-Jensen
2005-11-30 22:40 gcc help pati (sent by Nabble.com)
2005-11-30 23:04 ` Mike Stump
2010-05-18 18:11 packet
2010-05-18 18:18 ` Joel Sherrill

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='000901be2854$dc324b00$320171d8@enzo.videotron.ca' \
    --to=methote@videotron.ca \
    --cc=egcs@cygnus.com \
    /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).