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/53453] darwin linker expects both AT_name and AT_comp_dir debug notes Date: Thu, 24 May 2012 20:20:00 -0000 [thread overview] Message-ID: <bug-53453-4-retsYa9oG7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53453-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53453 --- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-05-24 20:12:52 UTC --- It is correct and desirable. If you really need and we want to continue the endless stream of workarounds for Darwin toolchain bugs, then you'd add some target macro TARGET_FORCE_AT_COMP_DIR or similar, define it in darwin.h and if non-zero, force addition of the attribute even when the filename is absolute.
next prev parent reply other threads:[~2012-05-24 20:14 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-22 13:27 [Bug debug/53453] New: " howarth at nitro dot med.uc.edu 2012-05-22 14:30 ` [Bug debug/53453] " howarth at nitro dot med.uc.edu 2012-05-22 14:40 ` howarth at nitro dot med.uc.edu 2012-05-22 14:41 ` jakub at gcc dot gnu.org 2012-05-22 23:32 ` howarth at nitro dot med.uc.edu 2012-05-22 23:55 ` jakub at gcc dot gnu.org 2012-05-24 13:54 ` howarth at nitro dot med.uc.edu 2012-05-24 19:41 ` howarth at nitro dot med.uc.edu 2012-05-24 19:55 ` howarth at nitro dot med.uc.edu 2012-05-24 20:20 ` jakub at gcc dot gnu.org [this message] 2012-05-24 23:27 ` howarth at nitro dot med.uc.edu 2012-05-25 5:54 ` howarth at nitro dot med.uc.edu 2012-05-25 6:04 ` mrs at gcc dot gnu.org 2012-05-25 13:03 ` howarth at nitro dot med.uc.edu 2012-05-25 13:41 ` howarth at nitro dot med.uc.edu 2012-05-30 0:08 ` mrs at gcc dot gnu.org 2012-05-30 1:37 ` mrs at gcc dot gnu.org 2013-04-17 7:17 ` ebotcazou at gcc dot gnu.org 2013-04-17 15:55 ` mrs at gcc dot gnu.org 2013-04-17 16:21 ` mrs 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-53453-4-retsYa9oG7@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).