public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/46749] gcc.dg/debug/pr41893-1.c -gdwarf-2 testsuite failures on darwin
Date: Wed, 01 Dec 2010 21:51:00 -0000	[thread overview]
Message-ID: <bug-46749-4-1QjWGw1S6A@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46749-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46749

--- Comment #16 from rguenther at suse dot de <rguenther at suse dot de> 2010-12-01 21:51:18 UTC ---
On Wed, 1 Dec 2010, iains at gcc dot gnu.org wrote:

> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46749
> 
> --- Comment #15 from Iain Sandoe <iains at gcc dot gnu.org> 2010-12-01 21:34:19 UTC ---
> splitting the command into compile and link steps will intentionally remove the
> dsymutil step -  thus making the problem 'go away' ...
> 
> dsymutil should _only_ be called if there is a source file on the c/l 
> (which would have its object deleted and thus be unavailable for debug).

Huh, ok.  But the spec seems to call it unconditionally in the 
link-command-spec when -g is visible.  At least I can't see how
a "source file" is matched (and we now definitely do find object
files as source for the link step).

And the issue is probably that we match on the intermediate link
command but execute only after that is finished.

Well, that dsymutil hack looks like a hack.


  parent reply	other threads:[~2010-12-01 21:51 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 17:43 [Bug debug/46749] New: " howarth at nitro dot med.uc.edu
2010-12-01 17:50 ` [Bug debug/46749] " howarth at nitro dot med.uc.edu
2010-12-01 18:05 ` howarth at nitro dot med.uc.edu
2010-12-01 18:44 ` rguenth at gcc dot gnu.org
2010-12-01 20:31 ` howarth at nitro dot med.uc.edu
2010-12-01 20:31 ` howarth at nitro dot med.uc.edu
2010-12-01 20:33 ` howarth at nitro dot med.uc.edu
2010-12-01 20:35 ` howarth at nitro dot med.uc.edu
2010-12-01 20:38 ` rguenth at gcc dot gnu.org
2010-12-01 20:46 ` iains at gcc dot gnu.org
2010-12-01 20:50 ` rguenth at gcc dot gnu.org
2010-12-01 20:59 ` howarth at nitro dot med.uc.edu
2010-12-01 21:11 ` iains at gcc dot gnu.org
2010-12-01 21:21 ` iains at gcc dot gnu.org
2010-12-01 21:24 ` rguenth at gcc dot gnu.org
2010-12-01 21:34 ` iains at gcc dot gnu.org
2010-12-01 21:51 ` rguenther at suse dot de [this message]
2010-12-01 21:53 ` iains at gcc dot gnu.org
2010-12-01 22:06 ` iains at gcc dot gnu.org
2010-12-02  8:53 ` rguenther at suse dot de
2010-12-02  9:10 ` iains at gcc dot gnu.org
2010-12-02  9:51 ` rguenther at suse dot de
2010-12-02 10:10 ` iains at gcc dot gnu.org
2010-12-02 10:14 ` iains at gcc dot gnu.org
2010-12-03  0:26 ` mrs at gcc dot gnu.org
2010-12-03 10:48 ` rguenther at suse dot de
2010-12-03 10:51 ` rguenther at suse dot de
2010-12-03 11:30 ` iains at gcc dot gnu.org
2010-12-03 12:11 ` iains at gcc dot gnu.org
2010-12-03 23:13 ` mikestump at comcast dot net
2010-12-03 23:21 ` rguenther at suse dot de
2010-12-04  0:18 ` mikestump at comcast dot net
2010-12-04  2:11 ` howarth at nitro dot med.uc.edu
2010-12-04  3:19 ` howarth at nitro dot med.uc.edu
2010-12-04 10:28 ` rguenther at suse dot de
2010-12-05 21:13 ` mikestump at comcast dot net
2010-12-05 21:57 ` rguenth at gcc dot gnu.org
2010-12-07  0:26 ` mrs at gcc dot gnu.org
2010-12-07  0:34 ` mrs at gcc dot gnu.org
2010-12-07  9:47 ` rguenth at gcc dot gnu.org
2010-12-07 13:21 ` joseph at codesourcery dot com
2010-12-07 16:34 ` mrs at gcc dot gnu.org
2010-12-07 16:42 ` mikestump at comcast dot net
2010-12-08 20:11 ` mrs at gcc dot gnu.org
2010-12-08 23:13 ` 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-46749-4-1QjWGw1S6A@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: link
Be 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).