From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Tadeus Prastowo <tadeus.prastowo@unitn.it>
Cc: Peter Breuer <ptb@inv.it.uc3m.es>,
Peter Breuer <Peter.T.Breuer@gmail.com>,
Liu Hao <lh_mouse@126.com>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: signed/unsigned integer conversion for right shift seems
Date: Tue, 06 Feb 2018 18:47:00 -0000 [thread overview]
Message-ID: <CAH6eHdReC3g7SsOjq4Pp9Cr1grYwCwWesOmMCpcNPej9pheY4Q@mail.gmail.com> (raw)
In-Reply-To: <CAN-HRFYiK7=qnuKXuLrM21ue=1_g315hTWxOdd9QiXDdz=rpsQ@mail.gmail.com>
On 6 February 2018 at 18:37, Tadeus Prastowo wrote:
> @Peter Breuer: it seems that you are not very knowledgeable about the
> internals of the C language. Hence, I would like to invite you to
> study this very good resource on the internals of the C language:
> http://publications.gbdirect.co.uk/c_book/.
And maybe find somewhere else to discuss it. "I don't understand the C
standard" is not a GCC problem, so doesn't belong on this mailing
list.
next prev parent reply other threads:[~2018-02-06 18:47 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 15:03 signed/unsigned integer conversion for right shift seems against C99 rule Peter Breuer
2018-02-06 15:21 ` Tadeus Prastowo
2018-02-06 15:29 ` signed/unsigned integer conversion for right shift seems against Peter T. Breuer
2018-02-06 15:38 ` Tadeus Prastowo
2018-02-06 16:17 ` Peter T. Breuer
2018-02-06 15:22 ` signed/unsigned integer conversion for right shift seems against C99 rule Alexander Monakov
2018-02-06 15:22 ` Liu Hao
2018-02-06 15:31 ` David Brown
2018-02-06 15:50 ` signed/unsigned integer conversion for right shift seems Peter T. Breuer
2018-02-06 15:57 ` Jonathan Wakely
2018-02-06 16:42 ` Peter T. Breuer
2018-02-06 16:45 ` Jonathan Wakely
2018-02-06 17:19 ` Peter T. Breuer
2018-02-06 17:35 ` Jonathan Wakely
2018-02-06 18:23 ` Peter T. Breuer
2018-02-06 18:27 ` Jonathan Wakely
2018-02-06 18:37 ` Tadeus Prastowo
2018-02-06 18:47 ` Jonathan Wakely [this message]
2018-02-06 19:43 ` Peter T. Breuer
2018-02-06 20:08 ` Tadeus Prastowo
2018-02-06 20:15 ` Jonathan Wakely
2018-02-07 9:59 ` Peter T. Breuer
2018-02-07 12:28 ` David Brown
[not found] ` <201802071634.w17GYiEL000904@nbd.it.uc3m.es>
2018-02-07 16:39 ` Jonathan Wakely
2018-02-07 17:25 ` Peter T. Breuer
2018-02-07 17:39 ` Tadeus Prastowo
2018-02-07 18:50 ` Peter T. Breuer
2018-02-07 17:39 ` Jonathan Wakely
2018-02-07 18:32 ` Peter T. Breuer
2018-02-07 18:41 ` Jonathan Wakely
2018-02-07 18:11 ` Jonathan Wakely
2018-02-06 19:28 ` Peter T. Breuer
2018-02-06 20:11 ` Jonathan Wakely
2018-02-06 23:49 ` Peter T. Breuer
2018-02-07 2:04 ` Vincent Lefevre
2018-02-07 9:30 ` Peter T. Breuer
2018-02-06 21:18 ` Chris Hall
2018-02-06 17:44 ` Tadeus Prastowo
2018-02-06 19:00 ` Peter T. Breuer
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=CAH6eHdReC3g7SsOjq4Pp9Cr1grYwCwWesOmMCpcNPej9pheY4Q@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=Peter.T.Breuer@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=lh_mouse@126.com \
--cc=ptb@inv.it.uc3m.es \
--cc=tadeus.prastowo@unitn.it \
/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).