public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/43751] dsymutil is not called for fortran and, under some circumstances not for other FEs.
Date: Fri, 13 Dec 2013 15:18:00 -0000 [thread overview]
Message-ID: <bug-43751-4-WCmo3PD0WV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-43751-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43751
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |burnus at gcc dot gnu.org,
| |iains at gcc dot gnu.org
Resolution|FIXED |---
--- Comment #20 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
This PR has reappeared after r205679 with warnings of the kind
warning: DWARFDebugInfoEntry::AppendDependants() -- check on this item
TAG_namelist_item: attr = AT_namelist_item form = FORM_ref4
They are silenced with the following change of the regexp added at r167683:
--- gcc/testsuite/lib/prune.exp 2013-04-26 10:21:37.000000000 +0200
+++ ../work/gcc/testsuite/lib/prune.exp 2013-12-11 16:42:00.000000000 +0100
@@ -59,7 +59,7 @@ proc prune_gcc_output { text } {
# Ignore harmless warnings from Xcode 3.2.x.
regsub -all "(^|\n)\[^\n\]*ld: warning: can't add line info to anonymous
symbol\[^\n\]*" $text "" text
- regsub -all "(^|\n)\[^\n\]*warning:
DWARFDebugInfoEntry::AppendDependants\[^\n\]*AT_\[^\n\]*_bound\[^\n\]*FORM_ref4\[^\n\]*"
$text "" text
+ regsub -all "(^|\n)\[^\n\]*warning:
DWARFDebugInfoEntry::AppendDependants\[^\n\]*AT_\[^\n\]*FORM_ref4\[^\n\]*"
$text "" text
regsub -all "(^|\n)\[^\n\]*warning:\[^\n\]*TAG_variable:
AT_location\[^\n\]*didn't have valid function low pc\[^\n\]*" $text "" text
# Ignore harmless warnings from Xcode 4.0.
I hope this change will survive any fix for pr59438!
next prev parent reply other threads:[~2013-12-13 15:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-43751-4@http.gcc.gnu.org/bugzilla/>
2010-11-26 22:08 ` iains at gcc dot gnu.org
2010-11-27 9:55 ` iains at gcc dot gnu.org
2010-12-02 11:49 ` iains at gcc dot gnu.org
2010-12-02 22:27 ` mrs at gcc dot gnu.org
2010-12-03 8:58 ` iains at gcc dot gnu.org
2010-12-03 20:17 ` mikestump at comcast dot net
2010-12-03 22:32 ` rguenth at gcc dot gnu.org
2010-12-03 23:01 ` howarth at nitro dot med.uc.edu
2010-12-04 22:01 ` howarth at nitro dot med.uc.edu
2010-12-04 22:02 ` howarth at nitro dot med.uc.edu
2010-12-05 19:58 ` howarth at nitro dot med.uc.edu
2010-12-05 20:01 ` howarth at nitro dot med.uc.edu
2010-12-05 20:12 ` howarth at nitro dot med.uc.edu
2010-12-05 20:27 ` iains at gcc dot gnu.org
2010-12-10 12:41 ` iains at gcc dot gnu.org
2010-12-10 17:17 ` mrs at gcc dot gnu.org
2013-12-13 15:18 ` dominiq at lps dot ens.fr [this message]
2014-04-02 8:35 ` dominiq at gcc dot gnu.org
2014-04-04 6:44 ` dominiq at gcc dot gnu.org
2014-04-04 6:49 ` dominiq at lps dot ens.fr
2010-04-14 9:00 [Bug target/43751] New: " iains at gcc dot gnu dot org
2010-04-14 9:07 ` [Bug target/43751] " iains at gcc dot gnu dot org
2010-04-14 9:24 ` steven at gcc dot gnu dot org
2010-04-14 9:50 ` iains at gcc dot gnu dot org
2010-04-14 17:38 ` iains at gcc dot gnu dot 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-43751-4-WCmo3PD0WV@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).