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 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 14:18:00 -0000 [thread overview] Message-ID: <bug-59379-4-PgssSAt1jh@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 #19 from H.J. Lu <hjl.tools at gmail dot com> --- (In reply to Uroš Bizjak from comment #18) > 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. Yes, the resulting GCC works correctly. However, we generate extra (set (reg:DI) (zero_extend:DI (reg:SI))) It is because we generate (set (reg:SI) (reg:SI) (set (reg:DI) (zero_extend:DI (reg:SI))) REE pass doesn't know (set (reg:SI) (reg:SI) has an implicit ZERO_EXTEND. Here is a testcase: ---foo.c--- extern __thread unsigned int __bid_IDEC_glbflags; typedef unsigned long long UINT64; typedef __attribute__ ((aligned(16))) struct { UINT64 w[2]; } UINT128; extern UINT64 __bid64_from_uint64 (UINT64); extern void __bid_round64_2_18 (int q, int x, UINT64 C, UINT64 * ptr_Cstar, int *delta_exp, int *ptr_is_midpoint_lt_even, int *ptr_is_midpoint_gt_even, int *ptr_is_inexact_lt_midpoint, int *ptr_is_inexact_gt_midpoint); extern void __bid_round128_19_38 (int q, int x, UINT128 C, UINT128 * ptr_Cstar, int *delta_exp, int *ptr_is_midpoint_lt_even, int *ptr_is_midpoint_gt_even, int *ptr_is_inexact_lt_midpoint, int *ptr_is_inexact_gt_midpoint); UINT64 __bid64_from_uint64 (UINT64 x) { UINT64 res; UINT128 x128, res128; unsigned int q, ind; int incr_exp = 0; int is_midpoint_lt_even = 0, is_midpoint_gt_even = 0; int is_inexact_lt_midpoint = 0, is_inexact_gt_midpoint = 0; if (x <= 0x002386F26FC0ffffull) { if (x < 0x0020000000000000ull) { res = 0x31c0000000000000ull | x; } else { res = 0x6c70000000000000ull | (x & 0x0007ffffffffffffull); } } else { if (x < 0x16345785d8a0000ull) { q = 17; ind = 1; } else if (x < 0xde0b6b3a7640000ull) { q = 18; ind = 2; } else if (x < 0x8ac7230489e80000ull) { q = 19; ind = 3; } else { q = 20; ind = 4; } if (q <= 19) { __bid_round64_2_18 ( q, ind, x, &res, &incr_exp, &is_midpoint_lt_even, &is_midpoint_gt_even, &is_inexact_lt_midpoint, &is_inexact_gt_midpoint); } else { x128.w[1] = 0x0; x128.w[0] = x; __bid_round128_19_38 (q, ind, x128, &res128, &incr_exp, &is_midpoint_lt_even, &is_midpoint_gt_even, &is_inexact_lt_midpoint, &is_inexact_gt_midpoint); res = res128.w[0]; } if (incr_exp) ind++; if (is_inexact_lt_midpoint || is_inexact_gt_midpoint || is_midpoint_lt_even || is_midpoint_gt_even) *&__bid_IDEC_glbflags |= 0x00000020; if (res < 0x0020000000000000ull) { res = (((UINT64) ind + 398) << 53) | res; } else { res = 0x6000000000000000ull | (((UINT64) ind + 398) << 51) | (res & 0x0007ffffffffffffull); } } return(res);; } ----------- Compiling with -fPIC -O2, the differences between your patch and mine are --- bad.s 2014-01-19 06:10:28.006570325 -0800 +++ foo.s 2014-01-19 06:11:46.117754696 -0800 @@ -84,19 +84,18 @@ __bid64_from_uint64: movabsq $9007199254740991, %rax cmpq %rax, %rbx jbe .L23 - movl %ebp, %edx leaq 88(%rsp), %rsp .cfi_remember_state .cfi_def_cfa_offset 24 movabsq $2251799813685247, %rax - movl %edx, %edx + movl %ebp, %edx andq %rbx, %rax - movabsq $6917529027641081856, %rcx popq %rbx .cfi_def_cfa_offset 16 + movabsq $6917529027641081856, %rcx addq $398, %rdx - orq %rcx, %rax salq $51, %rdx + orq %rcx, %rax popq %rbp .cfi_def_cfa_offset 8 orq %rdx, %rax @@ -154,7 +153,6 @@ __bid64_from_uint64: leaq 88(%rsp), %rsp .cfi_remember_state .cfi_def_cfa_offset 24 - movl %eax, %eax addq $398, %rax salq $53, %rax orq %rbx, %rax My patch removes 2 extra (set (reg:DI) (zero_extend:DI (reg:SI))) >From gcc-bugs-return-440911-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 19 14:48:57 2014 Return-Path: <gcc-bugs-return-440911-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 9605 invoked by alias); 19 Jan 2014 14:48:55 -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 9553 invoked by uid 55); 19 Jan 2014 14:48:50 -0000 From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/59862] Code does not compile with 4.8.1 tarball release but compiles with 4.8.1 SVN release Date: Sun, 19 Jan 2014 14:48:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: other X-Bugzilla-Version: 4.8.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenther at suse dot de X-Bugzilla-Status: WAITING 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-59862-4-kfZFfiMHbl@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-59862-4@http.gcc.gnu.org/bugzilla/> References: <bug-59862-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/msg02053.txt.bz2 Content-length: 896 http://gcc.gnu.org/bugzilla/show_bug.cgi?idY862 --- Comment #7 from rguenther at suse dot de <rguenther at suse dot de> --- On Sun, 19 Jan 2014, dominiq at lps dot ens.fr wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?idY862 > > --- Comment #6 from Dominique d'Humieres <dominiq at lps dot ens.fr> --- > > The release tarball contain generated files so you don't need tools like > > flex or makeinfo to build GCC. Those are not present in SVN, so this is > > definitely not a packaging bug. > > Not sure to understand: gcc/gengtype-lex.c is in the tarball, but not in SVN. > From the above I understand that gcc/gengtype-lex.c should also not be in the > tarball. No, it is in the tarball so building does not require the tools to build it. > Is this correct? What could be the effect of gcc/gengtype-lex.c? That local flex is not used to build gengtype-lex.c from gengtype-lex.l
next prev parent reply other threads:[~2014-01-19 14:18 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 2014-01-19 14:18 ` hjl.tools at gmail dot com [this message] 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-PgssSAt1jh@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: linkBe 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).