public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/65435] UBsan runtime error reports in OpenSSL aes_core.c
Date: Mon, 16 Mar 2015 11:37:00 -0000	[thread overview]
Message-ID: <bug-65435-4-Z1VM6yImgv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65435-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
OpenSSL of course.  136 << 24 is not representable in int.
This is undefined behavior in C99/C11, and defined behavior in C++11.
Quoting C99 6.5.7/4:
"The result of E1 << E2 is E1 left-shifted E2 bit positions; vacated bits are
filled with zeros. If E1 has an unsigned type, the value of the result is E1 ×
2 ^ E2, reduced modulo one more than the maximum value representable in the
result type. If E1 has a signed type and nonnegative value, and E1 × 2 ^ E2 is
representable in the result type, then that is the resulting value; otherwise,
the behavior is undefined."
>From gcc-bugs-return-480433-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Mar 16 11:39:24 2015
Return-Path: <gcc-bugs-return-480433-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57970 invoked by alias); 16 Mar 2015 11:39:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 57935 invoked by uid 48); 16 Mar 2015 11:39:20 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/65427] [4.8/4.9/5 Regression] ICE in emit_move_insn with wide vector types
Date: Mon, 16 Mar 2015 11:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.9.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.8.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-65427-4-WGfF9JWNVD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65427-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65427-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-03/txt/msg01577.txt.bz2
Content-length: 209

https://gcc.gnu.org/bugzilla/show_bug.cgi?ide427

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I think the bug is that tree-vect-generic.c doesn't lower COND_EXPRs, only
VEC_COND_EXPRs.


  parent reply	other threads:[~2015-03-16 11:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-65435-4@http.gcc.gnu.org/bugzilla/>
2015-03-16 11:36 ` mpolacek at gcc dot gnu.org
2015-03-16 11:37 ` jakub at gcc dot gnu.org [this message]
2015-03-16 14:49 ` bernd.edlinger at hotmail dot de

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-65435-4-Z1VM6yImgv@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).