Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: mjbaars1977.gdb@gmail.com
Cc: mark.kettenis@xs4all.nl, dan@codesourcery.com,
	gdb-patches@sourceware.org,        gdb@sourceware.org
Subject: Re: print_npx_status_word
Date: Sat, 16 Apr 2011 17:10:00 -0000	[thread overview]
Message-ID: <201104161709.p3GH9KDB010026@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <4DA9C7FE.8020600@gmail.com> (mjbaars1977.gdb@gmail.com)

> Date: Sat, 16 Apr 2011 18:46:54 +0200
> From: "Baars, M.J." <mjbaars1977.gdb@gmail.com>
>
> >> When you look at the code in question more closely, you will see that it
> >> will present the content of the status word in more detail than the
> >> original function,
> > Which isn't necessarily a good thing.
> 
> I'll show you the difference in output after the 'info float' command.
> 
> original output:
> 
> Status Word:         0x0000
>                         TOP: 0
> 
> new and improved output:
> 
> status word              : 0x0000
>    exception flags        :
>    stack fault            : 0
>    error summary status   : 0
>    busy                   : 0
>    top of stack pointer   : 0
>    condition code         :
> 
> This will give you a much better overview of what is actually happing in 
> the numeric core, which is eventually what every programmer wants is 
> what I was always taught.

But it will add a lot of extra lines to the output of "info float"
such that it doesn't fit on a standard 24-line screen anymore.  The
current way of printing things is much more concise.  And your way of
printing things doesn't really add more information; it just uses more
words.  Admittedly to interpret the printed codes you probably need to
have the IA-32 Architecture Software Developer's manual at hand.  But
to be honest, if you're looking at the FPU at this detailed level you
probably already are reading that manual.


  reply	other threads:[~2011-04-16 17:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4DA7166F.10302@gmail.com>
     [not found] ` <m3aafshl6l.fsf@fleche.redhat.com>
     [not found]   ` <4DA7ED79.3000400@gmail.com>
     [not found]     ` <m3ei53efd8.fsf@fleche.redhat.com>
     [not found]       ` <4DA87235.7060003@gmail.com>
     [not found]         ` <m3pqoncw78.fsf@fleche.redhat.com>
     [not found]           ` <4DA87479.50203@gmail.com>
     [not found]             ` <m3lizbcvt7.fsf@fleche.redhat.com>
2011-04-16  6:09               ` print_npx_status_word Baars, M.J.
2011-04-16  8:24                 ` print_npx_status_word Mark Kettenis
2011-04-16 13:46                   ` print_npx_status_word Baars, M.J.
2011-04-16 14:29                     ` print_npx_status_word Daniel Jacobowitz
2011-04-16 16:21                       ` print_npx_status_word Baars, M.J.
2011-04-16 16:33                         ` print_npx_status_word Mark Kettenis
2011-04-16 16:47                           ` print_npx_status_word Baars, M.J.
2011-04-16 17:10                             ` Mark Kettenis [this message]
2011-04-16 17:55                               ` print_npx_status_word Baars, M.J.
2011-04-16 18:07                                 ` print_npx_status_word Marek Polacek
2011-04-18 17:00                               ` print_npx_status_word Tom Tromey
2011-04-16 16:45                         ` print_npx_status_word Eli Zaretskii
     [not found]                   ` <4DA99DA1.2090708__5871.13250880993$1302961604$gmane$org@gmail.com>
2011-04-18 17:04                     ` print_npx_status_word Tom Tromey
2011-04-19 19:01                       ` print_npx_status_word Baars, M.J.
2011-04-19 19:53                         ` print_npx_status_word Pedro Alves
2011-04-19 20:11                         ` print_npx_status_word Tom Tromey
2011-04-18 17:04                 ` print_npx_status_word Tom Tromey
2011-04-14 16:17 print_npx_status_word Baars, M.J.

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=201104161709.p3GH9KDB010026@glazunov.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=dan@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gdb@sourceware.org \
    --cc=mjbaars1977.gdb@gmail.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