Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Keith Thompson <kst-u@mib.org>
Newsgroups: comp.lang.c
Subject: Re: gcc failure (optimised/non-optimised)
Date: Thu, 04 May 2017 09:34:11 -0700
Organization: None to speak of
Lines: 34
Message-ID: <ln7f1weg3g.fsf@kst-u.example.com>
References: <odf2pf$dd0$1@dont-email.me> <58fb2265.5246218@news.xs4all.nl> <EEFKA.484957$fL.133530@fx24.am4> <lnzif8pi97.fsf@kst-u.example.com> <QlLKA.442109$Iy2.238516@fx28.am4> <oe4tco$g5p$1@dont-email.me> <unoNA.1049563$nT1.597350@fx44.am4> <vi5cgc51gojjifro1q2mqv8cir4lfgv6jn@4ax.com> <iopNA.363590$0L.286761@fx12.am4> <959d5007-8ac8-42f9-a6d9-b5e23feda0de@googlegroups.com> <oe5d3k$6fr$1@dont-email.me> <36d67442-8861-41b5-b5b3-f71681740e59@googlegroups.com> <oe7ge5$p9u$1@dont-email.me> <935683a9-7c2e-4f71-adcc-998d8a7fe0b4@googlegroups.com> <lnvapkh1eb.fsf@kst-u.example.com> <kZCOA.1178476$F83.296367@fx38.am4> <20170504121818.e12842fbcac72ff9662a2616@gmail.com> <KMDOA.89842$NT.64788@fx33.am4>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Info: mx02.eternal-september.org; posting-host="0e2e86081f18c92fbdd8e09f7dc96105"; logging-data="5948"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19X0nNltAHFbKinZzZO+zVo"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
Cancel-Lock: sha1:Khagjn1mQFaim1cVmQJbdItjCbQ= sha1:bmdiqoJbOg7qcCRiPQcq2p7/u5Q=
Xref: csiph.com comp.lang.c:109222

bartc <bc@freeuk.com> writes:
[...]
> There seem to be umpteen ways of denoting a type in the language, not 
> including the ones people invent for themselves:
>
> signed long long int          In code (excludes re-orderings, allowed
>                                omissions and, sometimes, repeats)
>
> int64_t                       stdint.h

Let me just point out, since you seem to be pretending not to be
aware of it, that long long int and int64_t are not necessarily
the same type.  int64_t is exactly 64 bits wide, while long long
int is *at least* 64 bits wide (though I've never heard of an
implementation where it's wider than 64 bits).  And int64_t can
be an alias for long rather than for long long -- as it is on the
implementation I mostly use.

[...]

> (Is there constant suffix such as '-LL' that can be used to denote a 
> constant of type int64_t for example?)

Not directly, but see the INT64_C() macro in N1570 7.20.4.1.
(It expands to a constant of type int_least64_t, not int64_t,
but with implicit conversions that generally doesn't matter.)
I know you think it's unbearably ugly and you'd rather invent your
own language to avoid using it, so you needn't bother saying so.

-- 
Keith Thompson (The_Other_Keith) kst-u@mib.org  <http://www.ghoti.net/~kst>
Working, but not speaking, for JetHead Development, Inc.
"We must do something.  This is something.  Therefore, we must do this."
    -- Antony Jay and Jonathan Lynn, "Yes Minister"