public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mark at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/98708] [11 Regression] cxx11-ios_failure-lt.s:36733: Error: file number less than one by r11-6755
Date: Sun, 17 Jan 2021 12:59:22 +0000 [thread overview]
Message-ID: <bug-98708-4-lu665ebrFZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98708-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98708
--- Comment #11 from Mark Wielaard <mark at gcc dot gnu.org> ---
Aha, now I see in libstdc++-v3/src/c++11/Makefile.am:
if ENABLE_DUAL_ABI
# Rewrite the type info for __ios_failure.
rewrite_ios_failure_typeinfo = sed -e
'/^_*_ZTISt13__ios_failure:/,/_ZTVN10__cxxabiv120__si_class_type_infoE/s/_ZTVN10__cxxabiv120__si_class_type_infoE/_ZTVSt19__iosfail_type_info/'
cxx11-ios_failure-lt.s: cxx11-ios_failure.cc
$(LTCXXCOMPILE) -S $< -o tmp-cxx11-ios_failure-lt.s
-test -f tmp-cxx11-ios_failure-lt.o && mv -f tmp-cxx11-ios_failure-lt.o
tmp-cxx11-ios_failure-lt.s
$(rewrite_ios_failure_typeinfo) tmp-$@ > $@
-rm -f tmp-$@
cxx11-ios_failure.s: cxx11-ios_failure.cc
$(CXXCOMPILE) -S $< -o tmp-$@
$(rewrite_ios_failure_typeinfo) tmp-$@ > $@
-rm -f tmp-$@
cxx11-ios_failure.lo: cxx11-ios_failure-lt.s
$(LTCXXCOMPILE) -g0 -c $< -o $@
cxx11-ios_failure.o: cxx11-ios_failure.s
$(CXXCOMPILE) -g0 -c $<
endif
Then my workaround of checking for debug_info_level > DINFO_LEVEL_NONE indeed
wouldn't work. It is explicitly generating debuginfo for the assembly file and
then adding -g0 when turning the assembly file into an object file. So that is
too late.
I don't think adding -gno-as-loc-support to the -S invocation will work because
of the definition of asm_outputs_debug_line_str () which is true if
dwarf_version >= 5 && ! output_asm_line_debug_info () &&
DWARF5_USE_DEBUG_LINE_STR. So then it will still generate the .file 0
directive.
Ideally gas wouldn't error on .file 0, but simply ignore it when not generating
DWARF5.
Maybe the simplest workaround for now would be also adding -g0 to the -S
invocations?
next prev parent reply other threads:[~2021-01-17 12:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 1:07 [Bug debug/98708] New: [11 Regression] cxx11-ios_failure-lt.s:36733: Error: file number less than one hjl.tools at gmail dot com
2021-01-17 1:10 ` [Bug debug/98708] " hjl.tools at gmail dot com
2021-01-17 3:51 ` [Bug debug/98708] [11 Regression] cxx11-ios_failure-lt.s:36733: Error: file number less than one by r11-6755 hjl.tools at gmail dot com
2021-01-17 4:50 ` hjl.tools at gmail dot com
2021-01-17 8:07 ` jakub at gcc dot gnu.org
2021-01-17 10:41 ` jakub at gcc dot gnu.org
2021-01-17 10:42 ` jakub at gcc dot gnu.org
2021-01-17 10:51 ` jakub at gcc dot gnu.org
2021-01-17 11:22 ` mark at gcc dot gnu.org
2021-01-17 12:25 ` jakub at gcc dot gnu.org
2021-01-17 12:40 ` hjl.tools at gmail dot com
2021-01-17 12:59 ` mark at gcc dot gnu.org [this message]
2021-01-17 13:31 ` mark at gcc dot gnu.org
2021-01-17 15:57 ` jakub at gcc dot gnu.org
2021-01-17 15:58 ` hjl.tools at gmail dot com
2021-01-17 16:02 ` jakub at gcc dot gnu.org
2021-01-17 16:22 ` jakub at gcc dot gnu.org
2021-01-18 10:29 ` cvs-commit at gcc dot gnu.org
2021-01-19 13:39 ` jakub 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-98708-4-lu665ebrFZ@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).