From: Robert Dubner <rdubner@symas.com>
To: "GCC Mailing List" <gcc@gcc.gnu.org>
Subject: RE: New feature -fdump-gimple-nodes
Date: Tue, 13 Feb 2024 13:04:46 -0600 (CST) [thread overview]
Message-ID: <094a01da5eaf$831aa460$894fed20$@symas.com> (raw)
In-Reply-To:
Oh, crap. This is *not* an auspicious beginning.
This message fragment was sent from Outlook, which does not have a good
working relationship with the e-mail handler my company uses. Please
ignore this while I painfully reconstruct the much longer message that
those two programs managed to lose, dammit.
Bob Dubner.
From: Robert Dubner <rdubner@symas.com>
Sent: Tuesday, February 13, 2024 14:01
To: 'GCC Mailing List' <gcc@gcc.gnu.org>
Subject: New feature -fdump-gimple-nodes
I have not contributed to GCC before, so I am not sure how to go about it.
So, I am letting you know what I want to do, so that I can get advice on
the best way to do it. I have read https://gcc.gnu.org/contribute.html,
and I have
Jim Lowden and I have been developing a COBOL front end for GCC. He's
primarily been parsing the language. It's been my task to generate the
GENERIC/GIMPLE trees for the parsed code. We've been working at this for
a couple of years. We have reached the point where we want to start
submitting patches for the community to evaluate.
I figured I would start small, where "small" means mainly one new source
code file of 1,580 lines.
next reply other threads:[~2024-02-13 19:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 19:04 Robert Dubner [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-13 19:00 Robert Dubner
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='094a01da5eaf$831aa460$894fed20$@symas.com' \
--to=rdubner@symas.com \
--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).