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 issue (gcc/hash-table.h|c) with --disable-checking [ introduced by r218976 ] Date: Thu, 21 May 2015 07:46:00 -0000 [thread overview] Message-ID: <bug-66038-4-7GifMldYOo@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 #21 from Richard Biener <rguenth at gcc dot gnu.org> --- (In reply to Douglas Mencken from comment #20) > I'm lost. “Vanilla” 5.1.0 configured without --disable-checking went thru > stage2 w/o any issue... That's interesting - we might run into a miscompilation here. Can you check with --disable-checking again but with just the gcc_checking_assert in hash_table_mod1 removed? Please also attach preprocessed source of genmatch.c for the stage2 build so it's possible to investigate that with a cross compiler. (preprocessed source with --disable-checking and the assert left in place) Btw, thanks for your help in tracking this down. I wonder if anybody tried a powerpc-linux bootstrap with --disable-checking... >From gcc-bugs-return-486879-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 21 07:48:38 2015 Return-Path: <gcc-bugs-return-486879-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 87748 invoked by alias); 21 May 2015 07:48:38 -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 87685 invoked by uid 55); 21 May 2015 07:48:33 -0000 From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/66211] [5/6 Regression] Rvalue conversion in ternary operator causes internal compiler error Date: Thu, 21 May 2015 07:48: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: 5.1.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenther at suse dot de X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.2 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-66211-4-ULbdk36f9S@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-66211-4@http.gcc.gnu.org/bugzilla/> References: <bug-66211-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: 2015-05/txt/msg01719.txt.bz2 Content-length: 445 https://gcc.gnu.org/bugzilla/show_bug.cgi?idf211 --- Comment #6 from rguenther at suse dot de <rguenther at suse dot de> --- On Wed, 20 May 2015, jakub at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?idf211 > > --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> --- > Perhaps just guard this particular match.pd pattern with GIMPLE guard for now > (until the delayed C++ folding is committed)? Will try.
next prev parent reply other threads:[~2015-05-21 7:46 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 ` rguenth at gcc dot gnu.org [this message] 2015-05-24 20:34 ` [Bug bootstrap/66038] [5 regression] (stage 2) build/genmatch issue (gcc/hash-table.h|c) with --disable-checking [ introduced by r218976 ] 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-7GifMldYOo@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).