From: Rafael Espindola <espindola@google.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Richard Guenther <richard.guenther@gmail.com>,
Diego Novillo <dnovillo@google.com>,
Paul Brook <paul@codesourcery.com>
Subject: Re: [patch] Fix PR41764
Date: Wed, 21 Oct 2009 22:46:00 -0000 [thread overview]
Message-ID: <38a0d8450910211517j4af51106qf3f81c169a7e830c@mail.gmail.com> (raw)
In-Reply-To: <38a0d8450910211055g4968b06fie72550732e1dcf4c@mail.gmail.com>
> OK if bootstraps and tests are OK?
Looks like this breaks debug generation for fortran:
gfortran.dg/debug/pr35154-dwarf2.f scan-assembler (DW_AT_name:
"__BLNK__"|"__BLNK__[^\n]*"[^\n]*DW_AT_name)
gfortran.dg/debug/pr35154-dwarf2.f scan-assembler (DW_AT_name:
"__BLNK__"|"__BLNK__[^\n]*"[^\n]*DW_AT_name)
gfortran.dg/debug/pr35154-dwarf2.f scan-assembler (DW_AT_name:
"label"|"label[^\n]*"[^\n]*DW_AT_name)
gfortran.dg/debug/pr35154-dwarf2.f scan-assembler (DW_AT_name:
"label"|"label[^\n]*"[^\n]*DW_AT_name)
gfortran.dg/debug/pr35154-dwarf2.f scan-assembler DIE[^\n]*DW_TAG_common_block
gfortran.dg/debug/pr35154-dwarf2.f scan-assembler DIE[^\n]*DW_TAG_common_block
gfortran.dg/debug/pr35154-dwarf2.f scan-assembler DIE[^\n]*DW_TAG_common_block
gfortran.dg/debug/pr35154-dwarf2.f scan-assembler DIE[^\n]*DW_TAG_common_block
gfortran.dg/debug/pr35154-stabs.f scan-assembler .stabs.*"__BLNK__",226
gfortran.dg/debug/pr35154-stabs.f scan-assembler .stabs.*"__BLNK__",228
gfortran.dg/debug/pr35154-stabs.f scan-assembler .stabs.*"label_",226
gfortran.dg/debug/pr35154-stabs.f scan-assembler .stabs.*"label_",228
gfortran.dg/debug/pr37738.f scan-assembler-times DIE[^\n]*DW_TAG_common_block 3
gfortran.dg/debug/pr37738.f scan-assembler-times DIE[^\n]*DW_TAG_common_block 3
Will try to debug, but could really use some help from someone that
knows fortran (and gfortran).
Cheers,
--
Rafael Ávila de Espíndola
next prev parent reply other threads:[~2009-10-21 22:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 18:09 Rafael Espindola
2009-10-21 22:46 ` Rafael Espindola [this message]
2009-10-26 18:53 ` Rafael Espindola
2009-10-28 4:24 ` Rafael Espindola
2009-10-28 14:27 ` Rafael Espindola
2009-10-28 19:20 ` Toon Moene
2009-10-28 19:37 ` Rafael Espindola
2009-10-28 14:34 ` Ian Lance Taylor
2009-10-28 20:38 ` Tobias Burnus
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=38a0d8450910211517j4af51106qf3f81c169a7e830c@mail.gmail.com \
--to=espindola@google.com \
--cc=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=paul@codesourcery.com \
--cc=richard.guenther@gmail.com \
/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).