The COBOL compiler has this routine:
void
gg_exit(tree exit_code)
{
tree the_call =
build_call_expr_loc(location_from_lineno(),
builtin_decl_explicit (BUILT_IN_EXIT),
1,
exit_code);
gg_append_statement(the_c
I am starting to bore
myself, I stop talking.
Thank you very much for the information about the hook, and thanks for a
little bit of insight into how to see what the compiler is doing.
Bob D.
> -Original Message-
> From: Richard Biener
> Sent: Friday, April 4, 2025 09:50
>
This program exhibits the behavior when compiled with -O2, -O3 and -OS
PROGRAM-ID. PROG.
PROCEDUREDIVISION.
MOVE 1 TO RETURN-CODE
STOP RUN.
> -Original Message-
> From: Richard Biener
> Sent: Friday, April 4, 2025 03:02
> To: R
>
> > So you want ECF_NORETURN and ECF_NOTHROW.
> >
> >> I stated that poorly. After I generate the GENERIC, and I hand the
> tree
> >> over to the middle end, it is the call to BUILT_IN_EXIT that seems to
> be
> >> disappearing.
> >>
> &g
m?
Thanks.
> -Original Message-
> From: Gcc On Behalf Of
Robert
> Dubner
> Sent: Thursday, April 3, 2025 18:19
> To: GCC Mailing List
> Subject: RE: COBOL: Call to builtin_decl_explicit (BUILT_IN_EXIT), is
> optimized away.
>
> I stated that poorly. After I gene
I stated that poorly. After I generate the GENERIC, and I hand the tree
over to the middle end, it is the call to BUILT_IN_EXIT that seems to be
disappearing.
Everything I describe here is occurring with a -O0 build of GCC and
GCOBOL.
> -Original Message-
> From: Robert Dubner
> -Original Message-
> From: Jakub Jelinek
> Sent: Saturday, March 15, 2025 13:38
> To: Robert Dubner
> Cc: GCC Mailing List ; James K. Lowden
> ; Richard Biener
> Subject: Re: COBOL test cases
>
> On Sat, Mar 15, 2025 at 12:20:14PM -0500, Robert Dubner wrot
> -Original Message-
> From: Jakub Jelinek
> Sent: Saturday, March 15, 2025 12:58
> To: Robert Dubner ; 'GCC Mailing List'
> ; 'James K. Lowden' ;
'Richard
> Biener'
> Subject: Re: COBOL test cases
>
> On Sat, Mar 15, 2025 at 05:3
> -Original Message-
> From: Jakub Jelinek
> Sent: Saturday, March 15, 2025 12:34
> To: Robert Dubner
> Cc: 'GCC Mailing List' ; 'James K. Lowden'
> ; 'Richard Biener'
> Subject: Re: COBOL test cases
>
> On Sat, Mar 15, 2025 at 1
I am struggling with the learning curves, here. I am trying to understand
dejagnu, and I am trying to understand tcl, and I am trying to understand
the testsuite chain of commands and files that result, somehow, in the
programs in testsuite/cobol.dg being executed. Dealing with three new
technolo
I anticipate making contributions to GCC on an ongoing basis, and
according to https://gcc.gnu.org/contribute.html, there are some forms
that need to be filled out by me and my employer for ".assignment.for all
future changes, and an employer disclaimer.".
I hereby request those forms.
Than
r two files.
Thanks again.
-Original Message-
From: Dimitar Dimitrov
Sent: Wednesday, February 14, 2024 11:31
To: Robert Dubner
Cc: 'GCC Mailing List'
Subject: Re: New feature: -fdump-gimple-nodes (once more, with feeling)
On Tue, Feb 13, 2024 at 01:46:11PM -0600, Rob
I have not contributed to GCC before, so I am not totally sure how to go
about it.
So, I am letting you know what I want to do, so that I can get advice on a
good way to do it. I have read https://gcc.gnu.org/contribute.html, and I
have reviewed the Gnu Coding Standards and the GCC additional cod
, dammit.
Bob Dubner.
From: Robert Dubner
Sent: Tuesday, February 13, 2024 14:01
To: 'GCC Mailing List'
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
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.
In the words of Nick Danger: "You just saved me a lot of investigative
work."
Thank you so much.
Bob D.
-Original Message-
From: Jakub Jelinek
Sent: Wednesday, January 10, 2024 15:51
To: Robert Dubner
Cc: 'GCC Mailing List'
Subject: Re: I am causing valgrind er
This message is a bit of a Hail Mary play. I am not asking anybody to spend
any real effort on this question; I am, instead, hoping that somebody will
say, "Oh, sure; you can fix that by doing so-and-so..." or "That happens
when the GENERIC tree is ..."
Jim Lowden and I are working on a COBOL
.section.rodata [...]
##
And that's exactly what I wanted.
Thanks for your help. It was your mention of "rest_of_compilation" that
ended this marathon investigation, and I really appreciate it.
Bob Dubner
-Original Message-
From: Gcc On
David, thank you very much. That looks very much like what I was hoping
for.
I'll dig into it tomorrow.
Heartfelt thanks,
Bob Dubner.
-Original Message-
From: David Malcolm
Sent: Monday, November 28, 2022 18:01
To: Robert Dubner ; gcc@gcc.gnu.org
Cc: 'Bob Dubner'
Su
I am part of a team working on a COBOL front end for GCC.
By reverse engineering other front ends, I learned, some months ago, how
to create a function_decl GENERIC node that is the root of a GENERIC tree
describing an entire function.
By calling the routine cgraph_node::finalize_function() wi
--
From: Andrew Pinski
Sent: Tuesday, October 4, 2022 15:03
To: Robert Dubner
Cc: gcc@gcc.gnu.org
Subject: Re: How do I create a GCC source code tarball?
On Mon, Oct 3, 2022 at 4:32 PM Robert Dubner wrote:
>
> I have modified the source code of GCC, and I need a tarball for that
> modifie
I have modified the source code of GCC, and I need a tarball for that
modified source.
My code is based on the trunk branch of the repository at
git://gcc.gnu.org/git/gcc.git
I attempted to execute "make dist", and have encountered the response
Building a full distribution of this tree isn
23 matches
Mail list logo
