public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/59379] [4.9 Regression] gomp_init_num_threads is compiled into an infinite loop with --with-arch=corei7  --with-cpu=slm
Date: Sun, 19 Jan 2014 09:51:00 -0000	[thread overview]
Message-ID: <bug-59379-4-ivz0rBcrEA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59379-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59379

--- Comment #18 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to H.J. Lu from comment #17)

> > I prefer first patch. It splits all LEAs, where ix86_avoid_lea_for_addr is
> > true.
> 
> Then we should avoid the extra
> 
> (set (reg:DI) (zero_extend:DI (reg:SI)))

ree pass, located just after post-reload split, should handle this extra
zero-extend insn. Based on this fact, we can just slap a zero-extend insn at
the end of sequence with:

--cut here--
Index: config/i386/i386.md
===================================================================
--- config/i386/i386.md (revision 206753)
+++ config/i386/i386.md (working copy)
@@ -5428,12 +5428,17 @@
   operands[0] = SET_DEST (pat);
   operands[1] = SET_SRC (pat);

-  /* Emit all operations in SImode for zero-extended addresses.  Recall
-     that x86_64 inheretly zero-extends SImode operations to DImode.  */
+  /* Emit all operations in SImode for zero-extended addresses.  */
   if (SImode_address_operand (operands[1], VOIDmode))
     mode = SImode;

   ix86_split_lea_for_addr (curr_insn, operands, mode);
+
+  /* Zero-extend return register to DImode for zero-extended addresses.  */
+  if (mode != <MODE>mode)
+    emit_insn (gen_zero_extendsidi2
+              (operands[0], gen_lowpart ((mode), operands[0])));
+
   DONE;
 }
   [(set_attr "type" "lea")
--cut here--

I have checked that this patch with the testcase from Comment #9, using "-O
-march=corei7 -mtune=slm" compile options. The resulting binary worked OK.
>From gcc-bugs-return-440882-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 19 10:03:59 2014
Return-Path: <gcc-bugs-return-440882-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4527 invoked by alias); 19 Jan 2014 10:03:58 -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 4489 invoked by uid 48); 19 Jan 2014 10:03:53 -0000
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/59867] Template string literal loses first symbol
Date: Sun, 19 Jan 2014 10:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: paolo.carlini at oracle dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-59867-4-ouCF3eXYOU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59867-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59867-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: 2014-01/txt/msg02024.txt.bz2
Content-length: 189

http://gcc.gnu.org/bugzilla/show_bug.cgi?idY867

--- Comment #9 from Paolo Carlini <paolo.carlini at oracle dot com> ---
Tuesday works for me ;) Seriously, thanks for looking into this.


  parent reply	other threads:[~2014-01-19  9:51 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-03 21:40 [Bug target/59379] New: " hjl.tools at gmail dot com
2013-12-03 21:46 ` [Bug target/59379] " octoploid at yandex dot com
2013-12-03 21:51 ` hjl.tools at gmail dot com
2013-12-03 21:52 ` hjl.tools at gmail dot com
2013-12-04  0:41 ` hjl.tools at gmail dot com
2013-12-04  0:48 ` hjl.tools at gmail dot com
2013-12-04 10:52 ` [Bug target/59379] [4.9 Regression] " hjl.tools at gmail dot com
2013-12-04 23:39 ` hjl.tools at gmail dot com
2013-12-05  3:11 ` hjl.tools at gmail dot com
2013-12-05 11:17 ` rguenth at gcc dot gnu.org
2013-12-06  1:45 ` hjl.tools at gmail dot com
2013-12-19 15:37 ` rguenth at gcc dot gnu.org
2013-12-26 12:41 ` izamyatin at gmail dot com
2013-12-26 12:57 ` hjl.tools at gmail dot com
2013-12-26 14:41 ` hjl.tools at gmail dot com
2013-12-30 21:16 ` izamyatin at gmail dot com
2013-12-31  7:02 ` izamyatin at gmail dot com
2014-01-18 17:13 ` hjl.tools at gmail dot com
2014-01-18 19:47 ` ubizjak at gmail dot com
2014-01-19  9:51 ` ubizjak at gmail dot com [this message]
2014-01-19 14:18 ` hjl.tools at gmail dot com
2014-01-19 15:48 ` uros at gcc dot gnu.org
2014-01-22 18:29 ` uros at gcc dot gnu.org
2014-01-22 18:40 ` ubizjak at gmail 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-59379-4-ivz0rBcrEA@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).