mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Jules Maselbas <jmaselbas@kalray.eu>
To: Sascha Hauer <sha@pengutronix.de>
Cc: Michael Olbrich <m.olbrich@pengutronix.de>, barebox@lists.infradead.org
Subject: Re: [PATCH] readline_simple: Fix compiler warning
Date: Wed, 12 May 2021 17:15:47 +0200	[thread overview]
Message-ID: <20210512151547.GB7003@tellis.lin.mbt.kalray.eu> (raw)
In-Reply-To: <20210512130430.GP19819@pengutronix.de>

FYI,

On Wed, May 12, 2021 at 03:04:30PM +0200, Sascha Hauer wrote:
> On Wed, May 12, 2021 at 01:25:14PM +0200, Michael Olbrich wrote:
> > On Wed, May 12, 2021 at 07:44:40AM +0200, Sascha Hauer wrote:
> > > char is an unsigned type.
> > 
> > That's incorrect. In the C standard it is explicitly undefined whether char
> > is signed or unsigned. gcc implements this differently depending on the
> > architecture. I think ARM and x86 differ here.
> 
> Ok. I already reworded this to "char can be an unsigned type".
You can use "singed char" if you really need it.

    There are five standard signed integer types, designated as signed char,
    short int, int, long int, and long long int.

from ISO/IEC 9899:TC2 - 6.2.5 Types

Best,
Jules


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox


      reply	other threads:[~2021-05-12 15:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12  5:44 Sascha Hauer
2021-05-12 11:25 ` Michael Olbrich
2021-05-12 13:04   ` Sascha Hauer
2021-05-12 15:15     ` Jules Maselbas [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=20210512151547.GB7003@tellis.lin.mbt.kalray.eu \
    --to=jmaselbas@kalray.eu \
    --cc=barebox@lists.infradead.org \
    --cc=m.olbrich@pengutronix.de \
    --cc=sha@pengutronix.de \
    /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