public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/67714] [6 Regression] signed char is zero-extended instead of sign-extended
Date: Fri, 25 Sep 2015 07:37:00 -0000	[thread overview]
Message-ID: <bug-67714-4-pNbBkANC9i@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67714-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67714

--- Comment #3 from ktkachov at gcc dot gnu.org ---
(In reply to kugan from comment #2)
> It is the same issue and the patch posted in
> https://gcc.gnu.org/ml/gcc-patches/2015-09/msg00403.html fixes this
> test-case too.

Thanks for checking!
I suppose you can reference this PR in that patches ChangeLog when it goes in


  parent reply	other threads:[~2015-09-25  7:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 15:06 [Bug middle-end/67714] New: [6 Regression] " ktkachov at gcc dot gnu.org
2015-09-24 16:17 ` [Bug middle-end/67714] [6 Regression] signed " kugan at gcc dot gnu.org
2015-09-25  4:58 ` kugan at gcc dot gnu.org
2015-09-25  7:37 ` ktkachov at gcc dot gnu.org [this message]
2015-09-25  7:53 ` rguenth at gcc dot gnu.org
2015-10-10 10:57 ` ramana at gcc dot gnu.org

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=bug-67714-4-pNbBkANC9i@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).