https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117009
Simon Sobisch changed:
What|Removed |Added
CC||simonsobisch at gnu dot org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119221
Simon Sobisch changed:
What|Removed |Added
CC||simonsobisch at gnu dot org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119336
--- Comment #3 from Simon Sobisch ---
Current output:
t.cob:1:25: error: could not open copybook file for '"notthere"'
1 | COPY "notthere".
| ^
t.cob:1:35: error: syntax error, unexpected '.', expecting
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119337
Simon Sobisch changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120621
Simon Sobisch changed:
What|Removed |Added
CC||simonsobisch at gnu dot org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121346
Bug ID: 121346
Summary: FR for dialect mf: support $DISPLAY
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: cobol
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121339
--- Comment #1 from Simon Sobisch ---
.. and the current diagnostic:
> error: DATA-ITEM 'FD-NAME' not found
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121339
Bug ID: 121339
Summary: extension CALL ... USING fd-name missing
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: cobol
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120772
Simon Sobisch changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120787
--- Comment #4 from Simon Sobisch ---
> If CHANGED is not important, we can emit a not-implemented warning and always
> print, changed or not.
This is what GnuCOBOL does, leading to:
* existing code compiles
* code does run, it "just" creates
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120772
--- Comment #4 from Simon Sobisch ---
While I agree with Sam that this commit was much too big, consisting of too
different things that would better have been split... this issue can be closed
now.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119331
--- Comment #4 from Simon Sobisch ---
I see, so I guess you'll leave enabling in the command line interface for now
and autogen+include a temporary CDF for disabling in cobcd?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120790
--- Comment #2 from Simon Sobisch ---
(In reply to James K. Lowden from comment #1)
> The local fix allows RECORD SEQUENTIAL instead of LINE SEQUENTIAL
> unconditionally.
you likely mean that one can use either, because RECORD SEQUENTIAL is ide
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120787
--- Comment #2 from Simon Sobisch ---
(In reply to James K. Lowden from comment #1)
> Can this not be resolved with
>>>COBOL-WORDS EQUATE DISPLAY WITH EXHIBIT
Plain EXHIBIT could, but EXHIBIT NAMED does not.
A force-included copybobok wit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120771
--- Comment #2 from Simon Sobisch ---
(In reply to James K. Lowden from comment #1)
> For the following input
>
> $IF C-OBS-ARCH = "x86"
> $if nested-missing = 7
> 77 something value "never".
> $else
> 77 s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120786
--- Comment #4 from Simon Sobisch ---
> The only accommodation I see here is to parse NOT -- i.e., `NOT=` and
friends, for algebraic symbols -- as two tokens.
Sounds good (and will solve a bunch of syntax errors I've received).
But would that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120786
--- Comment #2 from Simon Sobisch ---
Just keep in mind that a , and ; are valid separators as well, not only spaces
(they can be inserted nearly every place where a space can, with the exception
of places where they are required).
Rechecked wi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120804
--- Comment #1 from Simon Sobisch ---
happening in general, not only with literals:
error: invalid SET T02-IND (FldNumericDisplay) TO T01-IND (FldNumericDisplay):
not a field index
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120804
Bug ID: 120804
Summary: FR: allow SET of numeric-display variables
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: cobol
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120796
Bug ID: 120796
Summary: FR support non-standard REDEFINES position
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: cobol
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120769
--- Comment #3 from Simon Sobisch ---
The issue at hand is that the command line is constructed from "defaults",
which may include a fixed form request; and then later on the user overrides
and want to use auto-detection. To your good outlined r
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120794
Bug ID: 120794
Summary: extra separator periods lead to syntax error
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: cob
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120793
Bug ID: 120793
Summary: FR gcobc: handle -fnot-reserved
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: cobol
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120791
Bug ID: 120791
Summary: FR: support for MOVEing pointer to pointer
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: cobol
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120790
Bug ID: 120790
Summary: parser bug: ORGANIZATION IS RECORD SEQUENTIAL
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120787
Bug ID: 120787
Summary: FR: EXHIBIT + EXHIBIT named support
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: cobol
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120786
Bug ID: 120786
Summary: strange message for NOT=
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: cobol
Assigne
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120779
Bug ID: 120779
Summary: HIGH-VALUE / LOW-VALUE not found
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: cobol
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120769
--- Comment #1 from Simon Sobisch ---
Note: the auto format seems to not work any more, after getting errors with *
in col 7 I had to manually switch to use "gcobc -fixed".
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119337
Simon Sobisch changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120771
Bug ID: 120771
Summary: CDF broken
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: cobol
Assignee: unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120772
Bug ID: 120772
Summary: gcobc requires explicit -fPIC
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: cobol
As
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120769
Bug ID: 120769
Summary: cobol frontend - provide a way to undo -ffixed-form /
-ffree-form
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119331
--- Comment #2 from Simon Sobisch ---
This issue keep up popping in each test run :-/
Current output of
gcobc --debug -fno-ec=DATA-INCOMPATIBLE -fno-ec=PROGRAM-ARG-MISMATCH
-fno-ec=PROGRAM-ARG-OMITTED
warning: --debug implies -fstack-check:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120768
Bug ID: 120768
Summary: cdf-includes: strange line numbers
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: cobol
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120767
Bug ID: 120767
Summary: cdf-includes: needs to work in any source format (use
of floating comment indicators
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Sev
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120765
Bug ID: 120765
Summary: gcobc broken shellscript
Product: gcc
Version: 16.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: cobol
Assigne
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120715
--- Comment #1 from Simon Sobisch ---
Note: the sample was mostly copied from the Annex D of COBOL2023, but I believe
that to be in error and the right version to be
EDITING CHARACTER L FOR NEGATIVE IS "("
EDITING CHARACTER F FOR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120715
Bug ID: 120715
Summary: FR: add COBOL2023 EDITING phrase to PICTURE clause
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120623
Simon Sobisch changed:
What|Removed |Added
CC||simonsobisch at gnu dot org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120422
Simon Sobisch changed:
What|Removed |Added
CC||simonsobisch at gnu dot org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119636
--- Comment #5 from Simon Sobisch ---
Note: While I'm all for cleaning up COBOL code, we do run some programs that
still have that in... ignoring (possibly with a warning, but for other
compilers you have to enable outputting those) would be muc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119933
Simon Sobisch changed:
What|Removed |Added
CC||simonsobisch at gnu dot org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119805
--- Comment #5 from Simon Sobisch ---
I possibly need to wait one day more (just tested with the godbolt snapshot
from yesterday)... but there:
* compiles as expected with dialects gnu and mf
* raises the same error message without dialect or w
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119769
Simon Sobisch changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120417
--- Comment #11 from Simon Sobisch ---
Note: it only does not work with optimizations... but I understand the point of
UB - seems we got "away lucky" since quite some time for this, but with C23
default the function pointers need to be adjusted
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120417
--- Comment #9 from Simon Sobisch ---
Checked -fstack-reuse=none - same abort.
The main issue here is the language this C code has to cover: COBOL allows for
any trailing arguments to be "left out".
If the COBOL compiler knows about the paramet
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120417
--- Comment #7 from Simon Sobisch ---
UB may be necessary to trigger that (and with GCC+libc that _does_ work on all
environments but GNU/Linux 32bit [in theory it could also be multiarch -m32,
but I think that should not make a difference]) :-/
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120417
--- Comment #4 from Simon Sobisch ---
@sjames: What do you mean with "needs reduction"? And do you intend to do it on
your own?
[Note: I've reduced the original program that was generated from as much as
possible, then also reduced the amount o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120417
--- Comment #3 from Simon Sobisch ---
Created attachment 61511
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61511&action=edit
save-temps: preprocessed and assembly
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120417
--- Comment #2 from Simon Sobisch ---
I'll provide the result of --save-temps later, so you see both the .i and .s
files.
Note that to link and run the code you'd have to have a matching GnuCOBOL
installation (linked tarball has 5MB and only li
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119457
--- Comment #2 from Simon Sobisch ---
I tend to disagree as the referenced one is explicit about MOVE (and of course
using matching type assignments and functions, possibly split like for strings
using memcpy+memset for space is most reasonable
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119633
--- Comment #2 from Simon Sobisch ---
Nearly agreed. As long as there is no "WITH DEBUGGING" active (which you can
warn or even error on) an indicator D is, just as a * or a / an indicator
defining that the line has no executable code.
It can a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120402
--- Comment #2 from Simon Sobisch ---
Yes, U as per currently IBM (the COBOL Development group is in the process of
adding it for the next standard).
To handle the precedence - feel free to copy GnuCOBOL's implementation in
cobc/tree.c, especia
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119454
--- Comment #3 from Simon Sobisch ---
The "how to create a bug report" is identical for all GCC frontends (so far).
It is documented at https://gcc.gnu.org/bugs/#detailed
> In general, all the information we need can be obtained by collecting t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120417
Bug ID: 120417
Summary: gcc -m32 -O1 codegen error, leading to SIGSEGV,
workaround -fno-tree-coalesce-vars
Product: gcc
Version: 14.2.0
Status: UNCONFIRMED
Sev
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120402
Bug ID: 120402
Summary: gcobol does not check precedence of PIC characters
Product: gcc
Version: 13.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120401
Bug ID: 120401
Summary: gcobol allows arithmetic on alphanumeric fields
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119805
--- Comment #2 from Simon Sobisch ---
... no, only fails without dialect; with gnu/ibm now compiles
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119768
--- Comment #1 from Simon Sobisch ---
still happens; note: for improved error handling the "guessed
Alphanumeric-edited" could be used to internally define nat, for example as
plain PIC X, that would prevent the second error
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119805
--- Comment #1 from Simon Sobisch ---
still failing with today's package
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119821
Simon Sobisch changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119883
Simon Sobisch changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119638
--- Comment #2 from Simon Sobisch ---
Ooops - current debian package results in
gcobol tests/cobol85/SQ/SQ207M.CBL
(null):0: confused by earlier errors, bailing out
That seems like a sever bug (@jklowden: feel free to create a new one for th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119634
--- Comment #1 from Simon Sobisch ---
rechecked with today's debian package (now gcc 16), the result is identical,
also with -dialect ibm
Note: current versions still document the USE statement for procedures
https://www.ibm.com/docs/en/cobol-z
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119520
Simon Sobisch changed:
What|Removed |Added
Resolution|WORKSFORME |FIXED
--- Comment #2 from Simon Sobisch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119332
--- Comment #3 from Simon Sobisch ---
Instead of "/dev/null" you can also write "banana", it doesn't matter. Seems
like the option parsing is broken "somewhere".
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119256
Simon Sobisch changed:
What|Removed |Added
CC||simonsobisch at gnu dot org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119638
--- Comment #1 from Simon Sobisch ---
ping @jklowden
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119636
--- Comment #4 from Simon Sobisch ---
Please reopen as this is not about doing anything with the obsolete code in any
way, but ignoring = "parse in the water".
The main issue is that the FD is not recognized any more, and yes, there are a
lot o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119632
--- Comment #9 from Simon Sobisch ---
Note: GnuCOBOL also support that, just in case a paying customer comes around
:-)
To not break NIST85 gcobol should set -std=cobol85 to -dialect ibm, with the
current implementation.
(Note: "stacking" -dia
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119809
--- Comment #4 from Simon Sobisch ---
Looking forward to have a compiler targetting ISO COBOL to support that one day
:-)
Note: in C this would be a struct with int : 1, included, I think.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119810
--- Comment #3 from Simon Sobisch ---
Current GCC only raises that error if there is no NL after the final (which
seems an interesting bug as well), so you won't see that error with the code
example.
Just use DATA DIVI. (= a syntax error), may
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119632
--- Comment #7 from Simon Sobisch ---
I think
https://gitlab.cobolworx.com/COBOLworx/gcc-cobol/-/commit/9c2fcd3606662e550aea6173b06bc2a500b2ac52
is the right approach (adding a warning later, syntax-check if not iso,
otherwise abort).
But it sh
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119335
--- Comment #2 from Simon Sobisch ---
That's totally fine if those are _really_ the files read-in as copybooks (if
they were opened with an extension, then of course this should be in).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119769
Simon Sobisch changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolution|FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119632
--- Comment #5 from Simon Sobisch ---
@Bob, what do you think of committing that patch as it waits on one of the
COBOL maintainers (and later or work on supporting that - at least as
"ignored")?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119364
Simon Sobisch changed:
What|Removed |Added
CC||simonsobisch at gnu dot org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119887
Bug ID: 119887
Summary: runtime-switches are not documented / implemented (and
don't pass NC211A and others)
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Sev
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119886
Bug ID: 119886
Summary: runtime-switches are not documented / implemented (and
don
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Pr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119885
Bug ID: 119885
Summary: libgcobol: SQRT wrong argument check
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: cobol
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119883
Bug ID: 119883
Summary: codegen: recursive user-defined functions don't run
recursive
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119825
Simon Sobisch changed:
What|Removed |Added
CC||jklowden at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119825
--- Comment #2 from Simon Sobisch ---
looks like the error comes from name resolution and is also reproducible with a
much more simple
Program-id. NofBug.
Data division.
Working-storage section.
01 billTo.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119821
Bug ID: 119821
Summary: FE (parser): CONFIGURATION SECTION rejects valid code
- empty paragraphs
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: norma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119810
Bug ID: 119810
Summary: FE: -include does not unset "included from"
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: cobo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119331
--- Comment #1 from Simon Sobisch ---
Side note: there's a working patch for gcobc at
https://gcc.gnu.org/pipermail/gcc-patches/2025-April/680218.html which improves
it in general - but this part was explicit left out
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119809
Bug ID: 119809
Summary: FE internal_error internal compiler error: in
digits_from_float128, at cobol/genapi.cc:15293 (bit
data items)
Product: gcc
Version: 15.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119759
--- Comment #3 from Simon Sobisch ---
Note "Copyright (c) 2021-2025 Symas Corporation" is also part of several files,
for example gcc/gcobol/parse.y
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119805
Bug ID: 119805
Summary: COMP-5 / COMP-X issues
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: cobol
Assignee:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119777
--- Comment #6 from Simon Sobisch ---
Looks good to me (and yes, --include should be possible multiple times), but I
haven't tested this or am a maintainer for gcobol...
Seems -Wall and --verbose (or -v only?) are different beasts, then.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119793
Bug ID: 119793
Summary: FR FE (parser): addition of BASED-STORAGE SECTION
(Fujitsu)
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119790
Bug ID: 119790
Summary: FE (parser): CONSTANT AS figurative-constant broken
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compone
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119777
Simon Sobisch changed:
What|Removed |Added
CC||simonsobisch at gnu dot org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119772
Bug ID: 119772
Summary: FE: COBOL2025/2026 (original GnuCOBOL extension)
LENGTH OF usage-specification missing
Product: gcc
Version: 15.0
Status: UNCONFIRMED
S
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119771
Bug ID: 119771
Summary: FE (parser): CONSTANT AS LENGTH OF does
not error - but result in length of zero
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Sever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119770
Bug ID: 119770
Summary: FLOAT-DECIMAL support + "cannot MOVE '_stack1'"
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119769
Bug ID: 119769
Summary: FE: GnuCOBOL extension BINARY-C-LONG missing
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: cob
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119768
Bug ID: 119768
Summary: FE: parsing PIC N and NAT is broken
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: cobol
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119759
Bug ID: 119759
Summary: LICENSE file in gcc/cobol
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: cobol
Assign
1 - 100 of 131 matches
Mail list logo
