From: "Philippe De Muyter" <phdm@macqel.be>
To: law@cygnus.com
Cc: gcc2@cygnus.com, egcs@cygnus.com
Subject: Re: dwarf2out.c/ASM_OUTPUT_ASCII,ASM_OUTPUT_DWARF_STRING
Date: Mon, 01 Dec 1997 06:46:00 -0000 [thread overview]
Message-ID: <199712011446.PAA02035@mail.macqel.be> (raw)
In-Reply-To: <10079.880985697@hurl.cygnus.com>
> > 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.
Sorry, my wording was not clear enough. I only meant that I do not see
anything 'experimental' in the differences between the egcs and testgcc
versions of dwarf2out.c, and that it would thus be better if they were
identical. Can one of the maintainer for gcc/dwarf2out.c update the
testgcc version to be identiacl to the egcs version ?
prev parent reply other threads:[~1997-12-01 6:46 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 ` dwarf2out.c/ASM_OUTPUT_ASCII,ASM_OUTPUT_DWARF_STRING Jeffrey A Law
1997-12-01 6:46 ` Philippe De Muyter [this message]
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=199712011446.PAA02035@mail.macqel.be \
--to=phdm@macqel.be \
--cc=egcs@cygnus.com \
--cc=gcc2@cygnus.com \
--cc=law@cygnus.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).