public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/63837] [5 Regression] r217391 causes kernel build errors with GCC_COMPARE_DEBUG=1 Date: Wed, 19 Nov 2014 16:38:00 -0000 [thread overview] Message-ID: <bug-63837-4-EipbZVcRbB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63837-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63837 --- Comment #15 from Jakub Jelinek <jakub at gcc dot gnu.org> --- (In reply to Manuel López-Ibáñez from comment #13) > (In reply to Jakub Jelinek from comment #12) > > Preapproved with proper ChangeLog entry. > > Unfortunately, there seems to be a problem with the machine in the compile > farm that I use for gcc development, and I'm not able to finish a > bootstrap®ression test. I always get: I'm bootstrapping/regtesting your patch now, will apply if it succeeds. >From gcc-bugs-return-467532-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Nov 19 16:49:57 2014 Return-Path: <gcc-bugs-return-467532-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 12327 invoked by alias); 19 Nov 2014 16:49:57 -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 12268 invoked by uid 48); 19 Nov 2014 16:49:54 -0000 From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/63837] [5 Regression] r217391 causes kernel build errors with GCC_COMPARE_DEBUG=1 Date: Wed, 19 Nov 2014 16:49:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: driver X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: manu at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-63837-4-ZGSi96RXen@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-63837-4@http.gcc.gnu.org/bugzilla/> References: <bug-63837-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-11/txt/msg02004.txt.bz2 Content-length: 411 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63837 --- Comment #16 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #15) > I'm bootstrapping/regtesting your patch now, will apply if it succeeds. Thanks! The changelog could also mention PR driver/36312 so people complaining about this bug there get a notification when the patch is committed. >From gcc-bugs-return-467533-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Nov 19 16:54:18 2014 Return-Path: <gcc-bugs-return-467533-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 15768 invoked by alias); 19 Nov 2014 16:54:18 -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 15742 invoked by uid 48); 19 Nov 2014 16:54:14 -0000 From: "hp at tmm dot cx" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug jit/63969] New: gccjit segfaults when it can't locate the correct gcc driver program Date: Wed, 19 Nov 2014 16:54:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: jit X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: hp at tmm dot cx X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter Message-ID: <bug-63969-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-11/txt/msg02005.txt.bz2 Content-length: 1081 https://gcc.gnu.org/bugzilla/show_bug.cgi?idc969 Bug ID: 63969 Summary: gccjit segfaults when it can't locate the correct gcc driver program Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: jit Assignee: dmalcolm at gcc dot gnu.org Reporter: hp at tmm dot cx When running tut01-hello-world.c with a gccjit installed in a prefix, but PATH not pointing to a gcc-5.0.0 driver the program segfaults. $ LD_LIBRARY_PATH=/home/hp/Apps/gccjit/lib ./tut01-hello-world Segmentation fault It works correctly with a PATH set appropriately $ PATH=/home/hp/Apps/gccjit/bin:$PATH LD_LIBRARY_PATH=/home/hp/Apps/gccjit/lib ./tut01-hello-world hello world gcc trunk r217763, build options ../configure --enable-host-shared --enable-languages=jit --disable-bootstrap --enable-checking=release --prefix=/home/hp/Apps/gccjit make install'd It would be better if an error message was printed rather than a segmentation fault.
next prev parent reply other threads:[~2014-11-19 16:38 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-12 18:07 [Bug driver/63837] New: " trippels at gcc dot gnu.org 2014-11-12 23:56 ` [Bug driver/63837] " manu at gcc dot gnu.org 2014-11-13 2:41 ` trippels at gcc dot gnu.org 2014-11-13 2:47 ` pinskia at gcc dot gnu.org 2014-11-13 9:21 ` rguenth at gcc dot gnu.org 2014-11-13 9:57 ` trippels at gcc dot gnu.org 2014-11-13 13:36 ` manu at gcc dot gnu.org 2014-11-13 13:49 ` trippels at gcc dot gnu.org 2014-11-15 7:11 ` pinskia at gcc dot gnu.org 2014-11-15 11:16 ` manu at gcc dot gnu.org 2014-11-16 22:03 ` trippels at gcc dot gnu.org 2014-11-17 21:24 ` jakub at gcc dot gnu.org 2014-11-19 15:34 ` manu at gcc dot gnu.org 2014-11-19 15:40 ` trippels at gcc dot gnu.org 2014-11-19 16:38 ` jakub at gcc dot gnu.org [this message] 2014-11-19 18:12 ` jakub at gcc dot gnu.org 2014-11-19 18:38 ` trippels at gcc dot gnu.org
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-63837-4-EipbZVcRbB@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).