Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Jim Blandy <jimb@cygnus.com>, Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: Recognize bottom of stack on Linux
Date: Wed, 06 Feb 2002 16:09:00 -0000	[thread overview]
Message-ID: <3C61C5A8.1040100@cygnus.com> (raw)
In-Reply-To: <npu1sujttj.fsf@zwingli.cygnus.com>

> I'm curious as to why we can't just set this universally, or at least a
>> little more globally.  Most things that have a main () use it as a
>> normal main ().  I'd propose that we set it as the default frame chain,
>> and provide/document an option to ignore inside_main_func.
> 
> 
> Well, gdbarch is never supposed to change the default behavior of
> macros; this helps us convert pre-gdbarch targets incrementally.
> Simply turning on gdbarch for one's target ideally wouldn't change its
> behavior at all.


Yes, definitly.  Rule of least suprise, learnt from multi-arch experience.

However, that doesn't stop an independant change that does alter the 
default behavour.  cf. my proposed patch to change the default value of 
TARGET_LONG_DOUBLE_FORMAT to ieee_double from floatformat_unknown.

enjoy,
Andrew


  reply	other threads:[~2002-02-07  0:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-03 18:21 Jim Blandy
2002-02-03 19:21 ` Daniel Jacobowitz
2002-02-03 23:00   ` Michael Snyder
2002-02-05 11:58   ` Jim Blandy
2002-02-05 13:57     ` Daniel Jacobowitz
2002-02-06 11:24       ` Jim Blandy
2002-02-06 16:09         ` Andrew Cagney [this message]
2002-03-30 21:56         ` Daniel Jacobowitz
2002-02-03 22:15 ` Eli Zaretskii
2002-02-04 11:02 ` Kevin Buettner
2002-02-04 17:32   ` Andrew Cagney
2002-02-04 17:42     ` Kevin Buettner
2002-02-04 17:44       ` Daniel Jacobowitz
2002-02-04 17:57         ` Michael Snyder
2002-02-04 18:55           ` Daniel Jacobowitz
2002-02-05 11:52         ` Jim Blandy
2002-02-06 16:02           ` Andrew Cagney

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=3C61C5A8.1040100@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@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