From: Jeffrey A Law <law@cygnus.com>
To: "Philippe De Muyter" <phdm@macqel.be>
Cc: gcc2@cygnus.com (gcc mailing list), egcs@cygnus.com (egcs mailing list)
Subject: Re: dwarf2out.c/ASM_OUTPUT_ASCII,ASM_OUTPUT_DWARF_STRING
Date: Mon, 01 Dec 1997 06:13:00 -0000 [thread overview]
Message-ID: <10079.880985697@hurl.cygnus.com> (raw)
In-Reply-To: <199712011058.LAA00466@mail.macqel.be>
In message < 199712011058.LAA00466@mail.macqel.be >you write:
> Testing egcs, I do not get that failure, because one uses there
> ASM_OUTPUT_ASCII that has been carefully defined by many config files,
> but one uses it only if flag_debug_asm is not set !
Right.
While it's not the perfect 100% correct solution, it is practical -- very
few people will ever use flag_debug_asm, and those who do are exactly
the people who can (and will) figure out what's going wrong.
> PS : dwarf2out.c in egcs and testgcc are different for no reason :
> macro name, assert instead of if () abort(),...
No, it's for a good reason.
Using "assert.h" like the old dwarfout/dwarf2out code is extremely bad.
Consider what happens on systems which have gcc already installed, but
no __eprintf in their existing libgcc.a -- they fail to build because
the dwarf code picks up gcc's assert.h, which references __eprintf,
which doesn't exist in libgcc.a.
jeff
next prev parent reply other threads:[~1997-12-01 6:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-01 2:59 dwarf2out.c/ASM_OUTPUT_ASCII,ASM_OUTPUT_DWARF_STRING Philippe De Muyter
1997-12-01 6:13 ` Jeffrey A Law [this message]
1997-12-01 6:46 ` dwarf2out.c/ASM_OUTPUT_ASCII,ASM_OUTPUT_DWARF_STRING Philippe De Muyter
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=10079.880985697@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=gcc2@cygnus.com \
--cc=phdm@macqel.be \
/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).