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: Mon, 17 Nov 2014 21:24:00 -0000 [thread overview] Message-ID: <bug-63837-4-msKc33tKH9@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 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> --- (In reply to Manuel López-Ibáñez from comment #6) > Index: gcc.c > =================================================================== > --- gcc.c (revision 217457) > +++ gcc.c (working copy) > @@ -4047,11 +4047,12 @@ process_command (unsigned int decoded_op > read_cmdline_option (&global_options, &global_options_set, > decoded_options + j, UNKNOWN_LOCATION, > CL_DRIVER, &handlers, global_dc); > } > > - if (output_file && strcmp (output_file, "-")) > + if (output_file && strcmp (output_file, "-") > + && strcmp (output_file, HOST_BIT_BUCKET)) > { > int i; > for (i = 0; i < n_infiles; i++) > if ((!infiles[i].language || infiles[i].language[0] != '*') > && canonical_filename_eq (infiles[i].name, output_file)) > Index: toplev.c > =================================================================== > --- toplev.c (revision 217457) > +++ toplev.c (working copy) > @@ -940,11 +940,12 @@ init_asm_output (const char *name) > strcat (dumpname, ".s"); > asm_file_name = dumpname; > } > if (!strcmp (asm_file_name, "-")) > asm_out_file = stdout; > - else if (!canonical_filename_eq (asm_file_name, name)) > + else if (!canonical_filename_eq (asm_file_name, name) > + || !strcmp (asm_file_name, HOST_BIT_BUCKET)) > asm_out_file = fopen (asm_file_name, "w"); > else > /* Use fatal_error (UNKOWN_LOCATION) instead of just fatal_error to > prevent gcc from printing the first line in the current file. */ > fatal_error (UNKNOWN_LOCATION, > > If you can test it on your side, it would be helpful. Preapproved with proper ChangeLog entry. >From gcc-bugs-return-467084-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 17 21:25:46 2014 Return-Path: <gcc-bugs-return-467084-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 30100 invoked by alias); 17 Nov 2014 21:25:46 -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 29366 invoked by uid 48); 17 Nov 2014 21:25:39 -0000 From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/63815] [5 Regression] g++.dg/other/pr53811.C fails with -mcmodel=large -fpic Date: Mon, 17 Nov 2014 21:25:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub 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: cc Message-ID: <bug-63815-4-r5YkW5Jd8P@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-63815-4@http.gcc.gnu.org/bugzilla/> References: <bug-63815-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/msg01556.txt.bz2 Content-length: 387 https://gcc.gnu.org/bugzilla/show_bug.cgi?idc815 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #16 from Jakub Jelinek <jakub at gcc dot gnu.org> --- So fixed?
next prev parent reply other threads:[~2014-11-17 21:24 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 [this message] 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 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-msKc33tKH9@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).