public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/58687] "#line __LINE__ ..." changes subsequent line numbers Date: Wed, 30 Oct 2013 15:08:00 -0000 [thread overview] Message-ID: <bug-58687-4-jLYuytIlzm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58687-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58687 Manuel López-Ibáñez <manu at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |manu at gcc dot gnu.org --- Comment #10 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to Max TenEyck Woodbury from comment #9) > temporary file names, but I think that I can get past that. It just takes > hours for the builds to complete... If you are planning to do sporadic GCC development, it may be worthwhile to ask for an account in the Compile Farm http://gcc.gnu.org/wiki/CompileFarm (I could have never done any GCC development without it.) For building GCC and testing patches there are several scripts in contrib/. I also have my own: http://gcc.gnu.org/wiki/ManuelL%C3%B3pezIb%C3%A1%C3%B1ez?action=AttachFile&do=view&target=gccfarming >From gcc-bugs-return-433068-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Oct 30 15:09:08 2013 Return-Path: <gcc-bugs-return-433068-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 12118 invoked by alias); 30 Oct 2013 15:09:07 -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 12085 invoked by uid 48); 30 Oct 2013 15:09:03 -0000 From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/58876] No non-virtual-dtor warning in std::unique_ptr Date: Wed, 30 Oct 2013 15:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 4.8.1 X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: redi at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: <bug-58876-4-YvdRIDd4sV@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-58876-4@http.gcc.gnu.org/bugzilla/> References: <bug-58876-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: 2013-10/txt/msg02212.txt.bz2 Content-length: 685 http://gcc.gnu.org/bugzilla/show_bug.cgi?idX876 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org --- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> --- Actually we can use this around the definition of default_delete<> #pragma GCC diagnostic push #pragma GCC diagnostic warning "-Wsystem-headers" /// Primary template of default_delete, used by unique_ptr template<typename _Tp> struct default_delete { ... }; #pragma GCC diagnostic pop
next prev parent reply other threads:[~2013-10-30 15:08 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-10-11 3:47 [Bug preprocessor/58687] New: " mtewoodbury at gmail dot com 2013-10-23 7:16 ` [Bug preprocessor/58687] " mtewoodbury at gmail dot com 2013-10-25 19:01 ` mtewoodbury at gmail dot com 2013-10-25 22:56 ` mtewoodbury at gmail dot com 2013-10-26 13:39 ` mtewoodbury at gmail dot com 2013-10-26 21:15 ` pinskia at gcc dot gnu.org 2013-10-27 13:59 ` mtewoodbury at gmail dot com 2013-10-28 17:51 ` mtewoodbury at gmail dot com 2013-10-28 18:53 ` joseph at codesourcery dot com 2013-10-30 7:39 ` mtewoodbury at gmail dot com 2013-10-30 15:08 ` manu at gcc dot gnu.org [this message] 2013-10-30 17:59 ` mtewoodbury at gmail dot com 2013-10-30 18:13 ` joseph at codesourcery dot com 2013-10-30 19:43 ` mtewoodbury at gmail dot com 2013-10-31 18:00 ` mtewoodbury at gmail dot com 2013-11-04 14:14 ` mtewoodbury at gmail dot com 2013-11-04 18:18 ` joseph at codesourcery dot com 2013-11-19 16:08 ` mtewoodbury at gmail dot com 2013-11-19 16:37 ` joseph at codesourcery dot com 2013-11-28 22:52 ` jsm28 at gcc dot gnu.org 2013-11-29 4:52 ` mtewoodbury at gmail dot com 2013-11-29 16:57 ` joseph at codesourcery dot com 2013-11-29 22:49 ` mtewoodbury at gmail dot com 2013-11-30 0:04 ` joseph at codesourcery 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-58687-4-jLYuytIlzm@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).