public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/66038] [5 regression] (stage 2) build/genmatch segfaults in operand::gen_transform (gcc/hash-table.h:223)
Date: Tue, 12 May 2015 10:02:00 -0000 [thread overview]
Message-ID: <bug-66038-4-Rt5GI8to1u@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66038-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66038
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mikestump at comcast dot net
Target Milestone|--- |5.2
Summary|[5.1.0 regression] (stage |[5 regression] (stage 2)
|2) build/genmatch segfaults |build/genmatch segfaults in
|in operand::gen_transform |operand::gen_transform
|(gcc/hash-table.h:223) |(gcc/hash-table.h:223)
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Douglas Mencken from comment #5)
> (In reply to rguenther@suse.de from comment #4)
> > Can you build stage2 with debuginfo? (--without-build-config at
> > configure)
> >
> > That should imrpove the backtrace.
> >
> > Thanks,
> > Richard.
>
> Sure I can. Here you go:
>
> (gdb) bt
> #0 0x0000e208 in operand::gen_transform () at
> ../../gcc-5.1.0/gcc/hash-table.h:223
> #1 0x00008530 in get_operator (id=0x808bec "tcc_comparison") at
> ../../gcc-5.1.0/gcc/genmatch.c:1495
> #2 0x00009ef8 in parser::parse_operator_list (this=0xbffff698) at
> ../../gcc-5.1.0/gcc/genmatch.c:2941
> #3 0x0000d190 in parser::parse_pattern (this=0xbffff698) at
> ../../gcc-5.1.0/gcc/hash-table.h:223
> #4 0x0000e19c in parser::parser (this=0xbffff698, r_=0xbffff4f8) at
> ../../gcc-5.1.0/gcc/hash-table.h:223
> #5 0x0005f3ac in main (argc=3146720, argv=0xbffff4f8) at
> ../../gcc-5.1.0/gcc/genmatch.c:3711
> Current language: auto; currently c++
Huh, the line numbers don't make any sense.
I wonder what
ld warning: atom sorting error for operand::gen_transform(__sFILE*, char
const*, bool, int, char const*, capture_info*, dt_operand**, bool) and
hash_table<id_base, xcallocator, false>::find_with_hash(id_base const*,
unsigned int) in build/genmatch.o
means and if that explains things? Like it ends up calling the wrong
function because of a linker bug? Can you paste the linker command for
linking stage2 build/genmatch and the output when -v -Wl,-v -Wl,-debug is
appended?
As far as I understand ld on ppc-darwin is a GNU ld variant, correct?
I can't find anything in current binutils though. Mike?
next prev parent reply other threads:[~2015-05-12 10:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 16:28 [Bug bootstrap/66038] New: SIGSEGV at stage 2 build/genmatch --gimple ../../gcc-5.1.0/gcc/match.pd dougmencken at gmail dot com
2015-05-06 16:30 ` [Bug bootstrap/66038] " dougmencken at gmail dot com
2015-05-09 4:37 ` dougmencken at gmail dot com
2015-05-11 7:57 ` [Bug bootstrap/66038] SIGSEGV at stage 2 - build/genmatch fails in operand::gen_transform rguenther at suse dot de
2015-05-12 10:02 ` rguenth at gcc dot gnu.org [this message]
2015-05-13 15:21 ` [Bug bootstrap/66038] [5 regression] (stage 2) build/genmatch segfaults in operand::gen_transform (gcc/hash-table.h:223) dougmencken at gmail dot com
2015-05-15 10:11 ` dougmencken at gmail dot com
2015-05-18 0:33 ` dougmencken at gmail dot com
2015-05-19 10:53 ` dougmencken at gmail dot com
2015-05-20 5:40 ` dougmencken at gmail dot com
2015-05-20 7:34 ` rguenther at suse dot de
2015-05-20 10:21 ` dougmencken at gmail dot com
2015-05-20 10:30 ` dougmencken at gmail dot com
2015-05-20 10:35 ` schwab@linux-m68k.org
2015-05-20 11:27 ` rguenther at suse dot de
2015-05-20 15:44 ` dougmencken at gmail dot com
2015-05-20 15:50 ` jakub at gcc dot gnu.org
2015-05-20 19:14 ` dougmencken at gmail dot com
2015-05-21 7:46 ` [Bug bootstrap/66038] [5 regression] (stage 2) build/genmatch issue (gcc/hash-table.h|c) with --disable-checking [ introduced by r218976 ] rguenth at gcc dot gnu.org
2015-05-24 20:34 ` dougmencken at gmail dot com
2015-06-05 22:42 ` kumba at gentoo dot org
2015-07-16 9:18 ` rguenth at gcc dot gnu.org
2015-08-24 8:21 ` kumba at gentoo dot org
2015-08-25 8:14 ` rguenth at gcc dot gnu.org
2015-08-25 9:00 ` kumba at gentoo dot org
2015-08-25 9:09 ` rguenther at suse dot de
2015-09-10 9:33 ` dougmencken 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-66038-4-Rt5GI8to1u@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).