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 fortran/68040] [5/6 Regression] Internal compiler error: Error reporting routines re-entered. Date: Thu, 29 Oct 2015 23:09:00 -0000 [thread overview] Message-ID: <bug-68040-4-pc1pgojNA5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-68040-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68040 --- Comment #3 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to Dominique d'Humieres from comment #2) > > However, I would argue that this precise warning does not need to use > > %E and it could simply use %s, which will make it less dependent on trees > > and fix this bug without further changes in Fortran. > > Where should I do the change? #13 0x0000000100ca61f1 in decl_attributes (node=<optimized out>, attributes=<optimized out>, flags=<optimized out>) at ../../_clean/gcc/attribs.c:446 But you need to figure out how to get the const char* pointing to the attribute name from the tree passed to %E. >From gcc-bugs-return-500975-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Oct 29 23:13:00 2015 Return-Path: <gcc-bugs-return-500975-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 24015 invoked by alias); 29 Oct 2015 23:13:00 -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 23975 invoked by uid 48); 29 Oct 2015 23:12:56 -0000 From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/52192] GCC_CHECK_TLS doesn't detect native TLS on Solaris 8/9 Date: Thu, 29 Oct 2015 23:13:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: other X-Bugzilla-Version: 4.7.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dje at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cf_gcctarget short_desc Message-ID: <bug-52192-4-w5Qrx3y190@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-52192-4@http.gcc.gnu.org/bugzilla/> References: <bug-52192-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-10/txt/msg02530.txt.bz2 Content-length: 709 https://gcc.gnu.org/bugzilla/show_bug.cgi?idR192 David Edelsohn <dje at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target|*-*-solaris2.[89], |*-*-solaris2.[89] |powerpc-ibm-aix* | Summary|GCC_CHECK_TLS doesn't |GCC_CHECK_TLS doesn't |detect native TLS |detect native TLS on | |Solaris 8/9 --- Comment #4 from David Edelsohn <dje at gcc dot gnu.org> --- I guess never mind because this would require libstdc++ always to be built with -pthread.
prev parent reply other threads:[~2015-10-29 23:09 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-21 10:11 [Bug fortran/68040] New: " dominiq at lps dot ens.fr 2015-10-21 11:59 ` [Bug fortran/68040] " rguenth at gcc dot gnu.org 2015-10-28 22:50 ` dominiq at lps dot ens.fr 2015-10-29 4:37 ` dominiq at lps dot ens.fr 2015-10-29 23:09 ` manu at gcc dot gnu.org [this message]
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-68040-4-pc1pgojNA5@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).