From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: Olavi Esker <olavi.esker@gmail.com>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: int8_t lives matter
Date: Sat, 23 Dec 2023 10:35:17 +0000 [thread overview]
Message-ID: <CAH6eHdS6fOTimfeuYJdPscz3qwV=4iYHesAVU9h8tQ2As6rLww@mail.gmail.com> (raw)
In-Reply-To: <CA+=Sn1nmrTsGiqS5UjBiM=SBq5ekOB8ATaP=7_WxWvCUwxj2Xw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1940 bytes --]
On Fri, 22 Dec 2023, 22:04 Andrew Pinski via Gcc, <gcc@gcc.gnu.org> wrote:
> On Fri, Dec 22, 2023 at 1:54 PM Olavi Esker via Gcc <gcc@gcc.gnu.org>
> wrote:
> >
> > Hello,
> >
> > #include <iostream>
> > #include <cstdint>
> >
> > int main()
> > {
> > std::int8_t myInt{65};
> > myInt += 1;
> > std::cout << myInt;
> > }
> >
> > Guess what this returns?
> > Character "B".
> >
> > int main()
> > {
> > std::int8_t myInt{};
> > std::cin >> myInt;
> > std::cout << myInt;
> > }
> > This will also read a character, and
> > print the characters ascii value.
> > So if I give it 3, it read it as '3', and prints out 51.
> >
> >
> > The compiler gives no warning of this whatsoever with the flags:
> > "-std=c++20",
> > "-pedantic-errors",
> > "-Wall",
> > "-Wpedantic",
> > "-Wshadow",
> > "-Wcast-align",
> > "-Wlogical-op",
> > "-Wno-unused-parameter",
> > "-Weffc++",
> > "-Wextra",
> > "-Wconversion",
> > "-Wsign-conversion".
> >
> >
> > t does seem like a mistake to have `signed char` and `unsigned char`
> > display as characters rather than numbers, since `char` is a distinct
> type.
> > And so `char` could display as a character and the other two as integers.
> >
> > Wish you can change this.
>
> First this is the wrong email list, it should be sent to gcc-help@.
> Second, your subject line can be read as being offensive to some folks
> due to the use of the phrase "lives matter".
>
(The thread has moved to gcc-help now)
Third, this is what the C++ standard says it should be. And it might
> be better to be brought up to a C++ forum rather than one about the
> GCC implementation of the C++ standard.
>
> Thanks,
> Andrew Pinski
>
> >
> > Thanks.
> > OE
>
prev parent reply other threads:[~2023-12-23 10:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 21:53 Olavi Esker
2023-12-22 22:03 ` Andrew Pinski
2023-12-23 10:35 ` Jonathan Wakely [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH6eHdS6fOTimfeuYJdPscz3qwV=4iYHesAVU9h8tQ2As6rLww@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=olavi.esker@gmail.com \
--cc=pinskia@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).