public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dale Johannesen <dalej@apple.com>
To: Devang Patel <dpatel@apple.com>
Cc: gcc@gcc.gnu.org, Dale Johannesen <dalej@apple.com>
Subject: Re: Re:
Date: Sat, 25 Sep 2004 10:54:00 -0000	[thread overview]
Message-ID: <B162901D-0E9B-11D9-A7CE-000A95D7D16C@apple.com> (raw)
In-Reply-To: <9D4EDFF8-0E91-11D9-AC54-000393A91CAA@apple.com>


On Sep 24, 2004, at 6:24 PM, Devang Patel wrote:
> On Sep 24, 2004, at 5:58 PM, Dale Johannesen wrote:
>> I'm tracking down a crash I'm getting locally.  It's not clear yet 
>> this is connected,
>> but I see a tree of this form in the Gimple and SSA dumps:
>>
>>   *pTmp4<D6472> = __NAGf90_dcdivdc (*pTmp2<D6470>, *pTmp3<D6471>);
>>
>> The Gimple doc does not allow a pointer deref in a function argument.
>> Is is supposed to?
>
> It says CALL_EXPR arguments are valid LHS. So it allows. I am reading 
> comment at the beginning of tree-gimple.c

Thanks, I was looking at tree-ssa.texi:

call-stmt: CALL_EXPR
   op0 -> _DECL | '&' _DECL
   op1 -> arglist
arglist:
   NULL_TREE
   | TREE_LIST
       op0 -> val
       op1 -> arglist
val : _DECL | CONST

There seem to be a number of differences.   Apparently the 
tree-ssa.texi version is older, as it's
closer (but not identical) to the summit paper, but some nits have 
crept in.   The version in
tree-gimple.c doesn't seem to allow ADDR_EXPR, but clearly it has to:

  __NAGf90_write (6, &FMT_129<D6540>, -1, 0B, 0, 0);

IMO it is highly desirable for future development to have a clean 
definition.  I expect not everyone
shares MO, so I'll volunteer to clean this up, but I'll need help 
determining what it should say.  I propose to
put a single copy of it one place or the other (I'd prefer the texi 
file), with a pointer to the master copy
in the other place.  Comments?

       reply	other threads:[~2004-09-25  2:38 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <044DA5B8-0E8E-11D9-80A2-000A95D7CD40@apple.com>
     [not found] ` <9D4EDFF8-0E91-11D9-AC54-000393A91CAA@apple.com>
2004-09-25 10:54   ` Dale Johannesen [this message]
2004-09-25 11:14     ` Re: Daniel Berlin
2004-09-25 11:31     ` Re: Richard Henderson
2024-01-05  9:57 Nani Rodrigue
2024-01-05 10:34 ` Jonathan Wakely
2024-01-05 10:58   ` Re: LIU Hao
  -- strict thread matches above, loose matches on Subject: below --
2023-11-18 21:22 Zebediah Beck
2023-11-18 23:52 ` David Edelsohn
2023-11-18 23:57   ` Re: Zebediah Beck
2023-01-13  5:41 Re: father.dominic
2022-05-22 21:20 Skrab Skrab
2022-05-22 22:12 ` David Edelsohn
2021-06-12 23:32 nayeemislam031702
2021-06-12 23:35 ` Aaron Gyes
2011-09-23 22:54 Re: Lawrence Gutsin
2011-06-29 15:42 Re: nicole8509
     [not found] <20080618135807.GA15427@bromo.msbb.uc.edu>
2008-06-18 18:02 ` Mike Stump
2008-01-10 16:29 Selina Ewing
2005-08-01 14:18 Chunjiang Li
2005-08-01 14:37 ` Daniel Berlin
2005-07-15 21:22 Re: ИнфоПространство
     [not found] <m3d5q5b0pw.fsf@localhost.localdomain>
2005-06-29 18:48 ` Re: Bryce McKinlay
2005-06-29 20:40   ` Re: Mark Mitchell
2005-06-29 21:54     ` Re: Jeffrey A Law
2005-06-29 23:17       ` Re: Joe Buck
2005-06-29 21:57     ` Re: Geoffrey Keating
2005-06-29 23:43       ` Re: Aalokrai Porwal
2004-12-11  3:30 Re: Лада Власовна
2004-11-29  5:11 Re: Елена Климентьевна
2004-09-07 13:59 Problem with operand handling Richard Kenner
2004-09-07 14:41 ` Diego Novillo
2004-09-07 14:51   ` Andrew MacLeod
2004-09-07 15:46     ` Nathan Sidwell
2004-09-07 15:55       ` Re: Andrew MacLeod
     [not found] <200305221636.h4MGaLDA010075@mururoa.inria.fr>
2003-05-22 16:45 ` Re: Daniel Berlin
2002-10-18 16:20 Re: Josep Maria
2002-10-18 16:22 ` Re: Josep Maria
2002-09-04 22:16 Re: ZMSECTT-2
2001-12-10 19:14 Re: Richard Kenner
1998-04-08  2:13 No Subject Yuan Xie
1998-04-08 15:08 ` Jeffrey A Law
1998-03-27 15:18 No Subject Ken Faiczak
1998-03-31  0:46 ` Jeffrey A Law
1998-02-10  3:34 Re: Jochen Kuepper
1998-02-10 10:30 ` Re: Jeffrey A Law
1998-02-09 14:46 No Subject Jochen Kuepper
1998-02-09 15:37 ` Jeffrey A Law
1997-12-05 13:11 No Subject Thomas Weise
1997-12-06  9:23 ` Jeffrey A Law
1997-08-26 21:22 (no subject) Eliot Dresselhaus
1997-10-17 23:35 ` Jeffrey A Law

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=B162901D-0E9B-11D9-A7CE-000A95D7D16C@apple.com \
    --to=dalej@apple.com \
    --cc=dpatel@apple.com \
    --cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).