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] gomp_init_num_threads is compiled into an infinite loop with --with-arch=corei7 --with-cpu=slm
Date: Tue, 03 Dec 2013 21:51:00 -0000 [thread overview]
Message-ID: <bug-59379-4-2q92ToWvGe@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 #2 from H.J. Lu <hjl.tools at gmail dot com> ---
Symptom is msgfmt never stops:
30751 pts/0 t 43:26 msgfmt -o de.mo
/export/gnu/import/git/gcc/libstdc++-
30752 pts/0 R 64:42 msgfmt -o fr.mo
/export/gnu/import/git/gcc/libstdc++-
(gdb) info shared
>From To Syms Read Shared Object Library
0x0000003039808780 0x0000003039832a98 Yes (*)
/lib64/libgettextsrc-0.18.2.so
0x000000303941aad0 0x000000303948179c Yes (*)
/lib64/libgettextlib-0.18.2.so
0x000000303e408d10 0x000000303e426ea8 Yes (*) /lib64/libcroco-0.6.so.3
0x000000303901a260 0x00000030390af89c Yes (*) /lib64/libglib-2.0.so.0
0x0000003cf6606d50 0x0000003cf6620164 Yes (*) /lib64/libncurses.so.5
0x0000003cf4a0ce40 0x0000003cf4a188d8 Yes (*) /lib64/libtinfo.so.5
0x0000003cf4610160 0x0000003cf4643ad0 Yes (*) /lib64/libunistring.so.0
0x0000003cdda1f410 0x0000003cddb6269f Yes (*) /lib64/libc.so.6
0x00007f570fecc380 0x00007f570fed9467 Yes
/export/build/gnu/gcc-lto-fdo/build-x86_64-linux/x86_64-unknown-linux-gnu/libgomp/.libs/libgomp.so.1
0x0000003cdde05790 0x0000003cdde103b1 Yes (*) /lib64/libpthread.so.0
0x0000003ce2a2e870 0x0000003ce2b15060 Yes (*) /lib64/libxml2.so.2
0x0000003cde200ed0 0x0000003cde2019ce Yes (*) /lib64/libdl.so.2
0x0000003cdd600ae0 0x0000003cdd61ac5a Yes (*) /lib64/ld-linux-x86-64.so.2
0x0000003cdea02170 0x0000003cdea0e5f0 Yes (*) /lib64/libz.so.1
0x0000003ce1602f30 0x0000003ce16187a0 Yes (*) /lib64/liblzma.so.5
0x0000003cde6054b0 0x0000003cde66fbb6 Yes (*) /lib64/libm.so.6
(*): Shared library is missing debugging information.
(gdb)
next prev parent reply other threads:[~2013-12-03 21: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 [this message]
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
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-2q92ToWvGe@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).