Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Markus Deuling <deuling@de.ibm.com>
To: Ulrich Weigand <uweigand@de.ibm.com>, Daniel Jacobowitz <drow@false.org>
Cc: GDB Patches <gdb-patches@sourceware.org>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [patch]: Fix access to SPU registers for fortran
Date: Tue, 22 Apr 2008 09:40:00 -0000	[thread overview]
Message-ID: <480D747C.6040609@de.ibm.com> (raw)
In-Reply-To: <20080421202318.GB26164@caradoc.them.org>

[-- Attachment #1: Type: text/plain, Size: 1432 bytes --]

Hi,

Daniel Jacobowitz schrieb:
> On Mon, Apr 21, 2008 at 10:00:42PM +0200, Ulrich Weigand wrote:
>> 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?
> 
> I see.  I didn't realize we already had the % operator that did the
> necessary operation - I must have not found it when this was last
> discussed.
> 
> Maybe we could mention it in the Operators bit of the Fortran
> documentation, and there add that GDB allows it on unions?
> 


thanks for your comments. I added some lines to the documentation.
Is this ok ?

ChangeLog:

	* gdb.texinfo (Fortran Operators): Describe '%' operator.


-- 
  Markus Deuling
  GNU Toolchain for Linux on Cell BE
  deuling@de.ibm.com


[-- Attachment #2: diff-spu-fortran-ptype-doc --]
[-- Type: text/plain, Size: 631 bytes --]

diff -urpN src/gdb/doc/gdb.texinfo dev/gdb/doc/gdb.texinfo
--- src/gdb/doc/gdb.texinfo	2008-04-21 06:23:26.000000000 +0200
+++ dev/gdb/doc/gdb.texinfo	2008-04-22 07:10:59.000000000 +0200
@@ -9903,6 +9903,12 @@ of the second one.
 @item :
 The range operator.  Normally used in the form of array(low:high) to
 represent a section of array.
+
+@item %
+The access component operator.  Normally used to access elements in derived
+types.  Also suitable for unions.  As unions aren't part of regular fortran
+this can only happen when accessing a register that uses a gdbarch-defined
+union type.
 @end table
 
 @node Fortran Defaults

  reply	other threads:[~2008-04-22  5:16 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
2008-04-21 21:53       ` Daniel Jacobowitz
2008-04-22  9:40         ` Markus Deuling [this message]
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=480D747C.6040609@de.ibm.com \
    --to=deuling@de.ibm.com \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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