Re: GNU make 4.2.90 release candidate available

[Dennis Clarke]

On 8/28/19 5:08 AM, Andreas Schwab wrote:
> On Aug 27 2019, Dennis Clarke <address@hidden> wrote:
>
> > (1)  -std=9899:1999    This is the same as c99 and it merely means that
> > GCC *should* make every reasonable attempt to comply with the C99 code
> > specification.
>
> This also disables every extension over C, especially POSIX.

Is this a *bad* thing or a *good* thing ?  What is the actual language
dialect that GNU Make wishes to be compliant with is the real question.

Also ... really ?

On the Solaris 10 machines I think that both my self and Paul Eggert are
running the C99 compiler from Oracle Studio 12.6 with the -Xc flag :

    The default mode of the compiler is -std=c11 without
    the -pedantic flag.

    -Xc     (c = conformance) Issues errors and warnings for programs
            that use non-ISO C constructs. This option is strictly
            conformant ISO C without K&R C compatibility extensions.

https://docs.oracle.com/cd/E77782_01/html/E77788/bjapr.html#OSSCGbjask

However in the GCC world with anything flavour recent I see :

    By default, GCC provides some extensions to the C language
    that, on rare occasions conflict with the C standard.

    See Extensions to the C Language Family. Some features that
    are part of the C99 standard are accepted as extensions in C90
    mode, and some features that are part of the C11 standard
    are accepted as extensions in C90 and C99 modes. Use of
    the -std options listed above disables these extensions where
    they conflict with the C standard version selected.

Also :

    A new edition of the ISO C standard was published in 1999 as
    ISO/IEC 9899:1999, and is commonly known as C99. (While in
    development, drafts of this standard version were referred to
    as C9X.) GCC has substantially complete support for this
    standard version; see http://gcc.gnu.org/c99status.html for
    details.

    To select this standard, use -std=c99 or -std=iso9899:1999.


Well now I feel sick to my stomach for doing that but I already had
explained ( with apologies ) to Paul Smith and the context of the
whole discussion was to just toss out on the table this is what I
am doing, have been doing for years and maybe should keep on doing
but if this looks icky and wrong then let's discuss it :

    https://lists.gnu.org/archive/html/bug-make/2019-08/msg00071.html

The nice thing at my age is that I am so very fine with being wrong
and I was just going with the idea that we are working with some very
clear C flavour and I needed to know where we stand on linux boxen
and on FreeBSD ( with LLVM/Clang or GCC ) and on Solaris UNIX and on
some embedded FreeScale chip somewhere or RISC-V or whatever.


--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional