public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "collison at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64011] Fail to compile pr48335-2.c on  big-endian where bit insert instruction supported
Date: Tue, 10 Feb 2015 07:32:00 -0000	[thread overview]
Message-ID: <bug-64011-4-4WaJtFlQ7q@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64011-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from collison at gcc dot gnu.org ---
Author: collison
Date: Tue Feb 10 07:31:25 2015
New Revision: 220568

URL: https://gcc.gnu.org/viewcvs?rev=220568&root=gcc&view=rev
Log:
2015-02-10  Michael Collison  <michael.collison@linaro.org>

    Backport from trunk r219718.
    * expmed.c (store_bit_field_using_insv): Improve warning message.
    Use %wu instead of HOST_WIDE_INT_PRINT_UNSIGNED.

    2015-01-15  Jiong Wang  <jiong.wang@arm.com>

2015-02-10  Michael Collison  <michael.collison@linaro.org>

    Backport from trunk r219717.
    2015-01-15  Jiong Wang  <jiong.wang@arm.com>

    PR rtl-optimization/64011
    * expmed.c (store_bit_field_using_insv): Warn and truncate bitsize when
    there is partial overflow.

Modified:
    branches/linaro/gcc-4_9-branch/gcc/ChangeLog.linaro
    branches/linaro/gcc-4_9-branch/gcc/expmed.c


  parent reply	other threads:[~2015-02-10  7:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21  3:42 [Bug target/64011] New: Fail to compile pr48335-2.c on big-endian aarch64 chenshanyaoboy at gmail dot com
2014-11-27 14:40 ` [Bug target/64011] " ramana at gcc dot gnu.org
2014-12-17 18:01 ` jiwang at gcc dot gnu.org
2014-12-18 17:36 ` [Bug target/64011] Fail to compile pr48335-2.c on big-endian where bit insert instruction supported jiwang at gcc dot gnu.org
2015-01-16 10:15 ` jiwang at gcc dot gnu.org
2015-01-16 10:24 ` jiwang at gcc dot gnu.org
2015-02-10  7:32 ` collison at gcc dot gnu.org [this message]
2024-03-15 22:04 ` pinskia 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-64011-4-4WaJtFlQ7q@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).