From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFC: Slay COERCE_FLOAT_TO_DOUBLE
Date: Mon, 06 Jan 2003 22:43:00 -0000 [thread overview]
Message-ID: <3E1A0655.2050009@redhat.com> (raw)
In-Reply-To: <20021223203031.GA18990@nevyn.them.org>
> Stabs compilers (I only checked GCC and Sun Workshop CC, but those are the
> two major ones) emit the call-as type in the debug information. I.E. an
> unprototyped function taking a float argument will have a type signature
> that says it takes a double. So the easy thing to do for stabs is to set
> TYPE_FLAG_PROTOTYPED always, with appropriate commentary. I've done this.
> It caused a minor bit of testsuite churn, since some ()'s became (void)'s; I
> think that's OK, we know they are really void functions anyway.
Can you expand a bit here. When exactly do the () become (void)?
Looking at the changes to stabs, mdebug and hpread it appears to reverse
the default for all non dwarf* cases - assume prototyped rather than
un-prototyped? That's a pretty radical change and needs to be clearly
spelt out in at least the NEWS file.
(Like many people I'm back from a break and am only just getting to
these e-mails. This is probably why there were few responses earlier.)
Andrew
next prev parent reply other threads:[~2003-01-06 22:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-23 14:03 Daniel Jacobowitz
2002-12-24 11:39 ` Eli Zaretskii
2003-01-04 22:38 ` Daniel Jacobowitz
2003-01-06 22:43 ` Andrew Cagney [this message]
2003-01-07 18:16 ` Daniel Jacobowitz
2003-01-07 18:05 Michael Elizabeth Chastain
2003-01-08 0:20 ` Andrew Cagney
2003-01-08 0:47 ` Daniel Jacobowitz
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=3E1A0655.2050009@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.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