gcc/DATESTAMP not updated since 20231109

[Rainer Orth]

For the last couple of days (since 2023-11-09), gcc/DATESTAMP hasn't
been updated.

Rainer

-- 
-
Rainer Orth, Center for Biotechnology, Bielefeld University

Re: gcc/DATESTAMP not updated since 20231109

[Jakub Jelinek via Gcc]

On Tue, Nov 14, 2023 at 09:30:21AM +0100, Rainer Orth wrote:
> For the last couple of days (since 2023-11-09), gcc/DATESTAMP hasn't
> been updated.

I'll have a look.  Probably some bad commit again.

Jakub

Q

[Lê như Hiệp via Gcc]

Ds Được gửi từ iPhone của tôi là sư phụ phụ huynh tg

Re: Missing DWARF children for variable templates

[Jonathan Wakely via Gcc]

On Sat, 11 Nov 2023 at 02:06, Nima Hamidi via Gcc  wrote:
>
> Another similar issue is with alias templates. The following code:

Please report both cases to Bugzilla, thanks.


>
> ```
> template 
> struct Cls {
>  using ptr = T *;
> };
>
> template 
> using Cls_ptr = typename Cls::ptr;
>
> Cls_ptr ai;
> Cls_ptr af;
> ```
>
> produces
>
> ```
> < 1><0x0029> DW_TAG_typedef
>  DW_AT_type <0x003d>
>  DW_AT_name (indexed string: 0x0008)Cls_ptr
>  DW_AT_decl_file 0x0001 /main.cpp
>  DW_AT_decl_line 0x0007
> ```
>
> by  clang, but produces the following by gcc. (Note the difference in 
> DW_AT_name’s.)
>
> ```
> < 1><0x0044> DW_TAG_typedef
>  DW_AT_name Cls_ptr
>  DW_AT_decl_file 0x0001
>  DW_AT_decl_line 0x0007
>  DW_AT_decl_column 0x0007
>  DW_AT_type <0x0027>
> ```
> On Nov 10, 2023 at 7:59 PM -0600, Nima Hamidi , wrote:
> >
> > template 
> > struct Cls {
> >  static const int v = 0;
> > };
> >
> > template 
> > int constexpr Cls_v = Cls::v;
> >
> > int func() {
> >  return Cls_v + Cls_v;
> > }

gcc cobol status

[James K. Lowden]

When in November we turn back our clocks, then naturally do
programmers' thoughts turn to Cobol, its promise, and future.  

At last post, nine months ago, we were working our way through the
NIST CCVS/85 test suite.  I am pleased to report that process is
complete.  As far as NIST is concerned, gcobol is a Cobol compiler.  

For those keeping score at home, we're at 656 terminal symbols and
1636 yacc rules. Cobol is nothing if not a big language.  

NIST CCVS/85 includes: 

Basic Cobol grammar
Intrinsic functions
IPC support, in the form of called by and calling C modules
I/O for sequential, indexed, and relative-addressed files
Sorting and merging of files
Compiler Directing Facility functions

The NIST tests can be downloaded and executed using an included
Makefile.  They comprise 8846 tests in 348 files.

We have adopted the ISO 2023 Cobol specification as the standard we're
writing to.  gcobol also includes a few extensions to support syntax
that is specific to IBM and MicroFocus compilers, for features that are
widely used or still in use but since dropped by ISO.  

Significant effort went, and continues to go, into a relatively
new Cobol feature, not part of the 1985 standard: handling Exception
Conditions. Good examples are scarce, though, and we would be pleased
to work with anyone whose code depends on correct EC handling, or who
would like to use it and cannot because their compiler doesn't support
it.  

Cobol also has quite requirements for numerical precision.  To that
end, gcobol now uses the C _Float128 datatype.  The precision of
intermediate computed results grows as needed, and overflows and
truncation are signified (if enabled) through the EC mechanism. The
switch to _Float128 was a third pass over the computation statements
(ADD, SUBTRACT, MULTIPLY, DIVIDE, and COMPUTE) and the lucky user
benefits from our hard-won experience, in the form of much better
performance.  

Of course, no battle plan survives first contact with the enemy.  As the
gcobol community grows and new erroneous code is encountered, the
compiler's error messages continue to improve.  


Plans.

We want the direction of gcobol to be influenced by user interest.
Every Cobol shop relies on different variations and extensions to the
language. Early adopters have an opportunity to make their voices heard
and needs met.  Operators are standing by.  

On deck for 2024:

* User acceptance testing
* support for EXEC SQL
* modifications consequent to GCC review 
* updated gdb support

Home page: 
https://www.cobolworx.com/pages/cobforgcc.html
Packages:
https://gitlab.cobolworx.com/COBOLworx/gcc-cobol/-/packages/2
Repository, and Issue tracker:
https://gitlab.cobolworx.com/COBOLworx/gcc-cobol/-/tree/master+cobol

We are: 
  *  James K. Lowden  
Front of the front-end: lexer and parser
  *  Robert Dubner 
Back of the front-end: adapting Cobol to Gimple

Thank you for you kind attention.

--jkl