public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/64905] unsigned short is loaded with 4-byte load (movl)
Date: Wed, 04 Feb 2015 16:07:00 -0000	[thread overview]
Message-ID: <bug-64905-4-h7ZzPAFIHd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64905-4@http.gcc.gnu.org/bugzilla/>

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

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vmakarov at redhat dot com

--- Comment #5 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Uroš Bizjak from comment #4)
> It looks the failure is due to:
> 
> emit-rtl.c:  REGNO_POINTER_ALIGN (HARD_FRAME_POINTER_REGNUM) =
> STACK_BOUNDARY;
> 
> The testcase forces the pointer to %rbp (== HARD_FRAME_POINTER_REGNUM in the
> above line), so the predicate thinks that the value in %rbp is aligned,
> since %rbp has its REGNO_POINTER_ALIGN set to STACK_BOUNDARY.
> 
> Looks like generic RTL infrastructure problem to me, the
> REGNO_POINTER_ALIGNMENT of hard_frame_pointer should be cleared when H_F_P
> is omitted and reused.

Like this

diff --git a/gcc/ira.c b/gcc/ira.c
index ea2b69f..a7cf476 100644
--- a/gcc/ira.c
+++ b/gcc/ira.c
@@ -2313,6 +2313,8 @@ ira_setup_eliminable_regset (void)

   if (frame_pointer_needed)
     df_set_regs_ever_live (HARD_FRAME_POINTER_REGNUM, true);
+  else
+    REGNO_POINTER_ALIGN (HARD_FRAME_POINTER_REGNUM) = 0;

   COPY_HARD_REG_SET (ira_no_alloc_regs, no_unit_alloc_regs);
   CLEAR_HARD_REG_SET (eliminable_regset);
>From gcc-bugs-return-475996-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 04 16:39:41 2015
Return-Path: <gcc-bugs-return-475996-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27401 invoked by alias); 4 Feb 2015 16:39:41 -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 27329 invoked by uid 48); 4 Feb 2015 16:39:36 -0000
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64935] [5 Regression] compare debug failure during building of Linux kernel
Date: Wed, 04 Feb 2015 16:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: trippels 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: 5.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc target_milestone everconfirmed
Message-ID: <bug-64935-4-dlbnzZqwlp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64935-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64935-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-02/txt/msg00329.txt.bz2
Content-length: 695

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

Markus Trippelsdorf <trippels at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2015-02-04
                 CC|                            |mkuvyrkov at gcc dot gnu.org
   Target Milestone|---                         |5.0
     Ever confirmed|0                           |1

--- Comment #1 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
Started with r220316.
Creduce came up with an invalid testcase. Re-reducing...


  parent reply	other threads:[~2015-02-04 16:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 18:03 [Bug translation/64905] New: " r.ayrapetyan at samsung dot com
2015-02-02 18:55 ` [Bug target/64905] " hjl.tools at gmail dot com
2015-02-02 18:59 ` hjl.tools at gmail dot com
2015-02-02 21:40 ` hjl.tools at gmail dot com
2015-02-04 13:55 ` [Bug rtl-optimization/64905] " ubizjak at gmail dot com
2015-02-04 16:07 ` hjl.tools at gmail dot com [this message]
2015-02-04 19:35 ` hjl at gcc dot gnu.org
2015-02-04 19:37 ` hjl.tools at gmail dot com
2015-02-04 19:44 ` dominiq at lps dot ens.fr
2015-02-04 20:03 ` hjl.tools at gmail dot com
2015-02-05 10:04 ` dominiq at lps dot ens.fr
2015-02-05 10:08 ` ubizjak at gmail dot com
2015-02-05 10:37 ` uros at gcc dot gnu.org
2015-04-22 12:02 ` jakub at gcc dot gnu.org
2015-04-22 13:53 ` r.ayrapetyan at samsung dot com

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-64905-4-h7ZzPAFIHd@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).