* RE: New feature -fdump-gimple-nodes
@ 2024-02-13 19:04 Robert Dubner
0 siblings, 0 replies; 2+ messages in thread
From: Robert Dubner @ 2024-02-13 19:04 UTC (permalink / raw)
To: GCC Mailing List
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
* New feature -fdump-gimple-nodes
@ 2024-02-13 19:00 Robert Dubner
0 siblings, 0 replies; 2+ messages in thread
From: Robert Dubner @ 2024-02-13 19:00 UTC (permalink / raw)
To: 'GCC Mailing List'
[-- Attachment #1: Type: text/plain, Size: 671 bytes --]
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2024-02-13 19:04 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-02-13 19:04 New feature -fdump-gimple-nodes Robert Dubner
-- strict thread matches above, loose matches on Subject: below --
2024-02-13 19:00 Robert Dubner
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).