Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: deuling@de.ibm.com (Markus Deuling),
	        gdb-patches@sourceware.org (GDB Patches)
Subject: Re: [patch]: Fix access to SPU registers for fortran
Date: Mon, 21 Apr 2008 20:04:00 -0000	[thread overview]
Message-ID: <200804212000.m3LK0gFL008220@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20080421193652.GA23498@caradoc.them.org> from "Daniel Jacobowitz" at Apr 21, 2008 03:36:52 PM

Daniel Jacobowitz wrote:

> Not without documentation, please.  Syntax that doesn't come from
> Fortran (as far as I know) and isn't in the manual might as well not
> be there :-)

Hmmm, most of the output changes in Markus' patch actually bring the
output in line with correct Fortran syntax in the first place ;-)

The one addition is the representation of "union" types in the output;
this can never happen in regular Fortran, but can happen if you access
registers that use a gdbarch-defined union type.  This extension is
simply the "C_Union" marker; note that as far as the *parser* is
concerned, there is no syntax extension.

But I guess you're right that this extension should be documented.
I assume the right place would be somewhere in section 12.4.3 Fortran?

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2008-04-21 20:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-18 19:54 Markus Deuling
2008-04-21 19:43 ` Ulrich Weigand
2008-04-21 19:59   ` Daniel Jacobowitz
2008-04-21 20:04     ` Ulrich Weigand [this message]
2008-04-21 21:53       ` Daniel Jacobowitz
2008-04-22  9:40         ` Markus Deuling
2008-04-22 11:04           ` Eli Zaretskii
2008-04-22 12:14             ` Markus Deuling

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=200804212000.m3LK0gFL008220@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=deuling@de.ibm.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    /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