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 debug/65809] [5/6 Regression] FAIL: gcc.dg/debug/pr65771.c -gstabs+* -O* (test for excess errors) Date: Mon, 20 Apr 2015 10:34:00 -0000 [thread overview] Message-ID: <bug-65809-4-SyIUSYRmAm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65809-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65809 --- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> --- No, __emutls_v.a certainly is not a user variable, that is an artificial object, the thread local variable of course lives elsewhere. You could just drop the stabs for TLS vars on the floor, stabs really doesn't have extensions to describe the TLS vars. Like: --- gcc/dbxout.c 2015-02-04 23:36:33.875630546 +0100 +++ gcc/dbxout.c 2015-04-20 12:27:14.579948127 +0200 @@ -2999,6 +2999,8 @@ dbxout_symbol_location (tree decl, tree if (MEM_P (home) && GET_CODE (XEXP (home, 0)) == SYMBOL_REF) { + if (SYMBOL_REF_TLS_MODEL (XEXP (home, 0)) != TLS_MODEL_NONE) + return 0; if (TREE_PUBLIC (decl)) { int offs; The disadvantage of doing that is that (at least on x86_64-linux with -gstabs+), ptype a etc. will stop working, but one couldn't inspect the variables there either, you really need DWARF for that. p &a $3 = (struct S (*)[10]) 0x0 is of course wrong. So, I'd classify this as a buggy Apple toolchain, but the above patch might be just ok and not really break anything anyone cares about.
next prev parent reply other threads:[~2015-04-20 10:34 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-65809-4@http.gcc.gnu.org/bugzilla/> 2015-04-20 9:13 ` dominiq at lps dot ens.fr 2015-04-20 9:20 ` jakub at gcc dot gnu.org 2015-04-20 9:35 ` dominiq at lps dot ens.fr 2015-04-20 9:37 ` dominiq at lps dot ens.fr 2015-04-20 9:49 ` iains at gcc dot gnu.org 2015-04-20 10:34 ` jakub at gcc dot gnu.org [this message] 2015-04-20 10:47 ` iains at gcc dot gnu.org 2015-04-20 14:40 ` iains at gcc dot gnu.org 2015-04-20 14:48 ` jakub at gcc dot gnu.org 2015-04-20 15:06 ` iains at gcc dot gnu.org 2015-09-19 11:50 ` dominiq at lps dot ens.fr
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-65809-4-SyIUSYRmAm@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).