public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/66038] [5 regression] (stage 2) build/genmatch issue (gcc/hash-table.h|c) with --disable-checking [ introduced by r218976 ]
Date: Tue, 25 Aug 2015 09:09:00 -0000 [thread overview]
Message-ID: <bug-66038-4-TfIUouTgtE@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
--- Comment #28 from rguenther at suse dot de <rguenther at suse dot de> ---
On Tue, 25 Aug 2015, kumba at gentoo dot org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66038
>
> --- Comment #27 from Joshua Kinard <kumba at gentoo dot org> ---
> (In reply to Richard Biener from comment #26)
> > Don't hold your breath. Basically somebody who can reproduce it has to find
> > the root-cause and a fix.
>
> 4.9.3 works, and the problem appears specific to genmatch with the '--gimple'
> argument. I guess I can test to see if 5.0.0 is also affected, and then start
> diffing the genmatch.c files between working/non-working version to trace the
> problem down. That will be quicker than git bisecting on these machines (old
> SGI machines). Can't stay stuck on 4.9.x forever...
Can you also nail the issue down to using --disable-checking? For the
powerpc case I think we run into a miscompile of stage2 and thus
genmatch.c is really only the trigger and wouldn't be the place for
a fix (well, maybe a workaround is fine for the GCC 5 branch here)
next prev parent reply other threads:[~2015-08-25 9:09 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 ` [Bug bootstrap/66038] [5 regression] (stage 2) build/genmatch segfaults in operand::gen_transform (gcc/hash-table.h:223) rguenth at gcc dot gnu.org
2015-05-13 15:21 ` 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 [this message]
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-TfIUouTgtE@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).