This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Question on GIMPLE semantics and EH

From: Mark Mitchell <mark at codesourcery dot com>
To: Paul Brook <paul at codesourcery dot com>
Cc: gcc at gcc dot gnu dot org, Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>, rth at redhat dot com
Date: Sun, 15 Aug 2004 17:33:27 -0700
Subject: Re: Question on GIMPLE semantics and EH
Organization: CodeSourcery, LLC
References: <10408132326.AA17778@vlsi1.ultra.nyu.edu> <200408140034.29134.paul@codesourcery.com>

Paul Brook wrote:

On Saturday 14 August 2004 00:26, Richard Kenner wrote:
   I don't suppose F36b has DECL_ARTIFICIAL set?  If it does, then
   that would explain the mistake -- the gimplifier thinks it
   already *is* a temporary.
I can confirm that not setting it fixes this ACATS test and a few others.
Is this intended as a long-term solution or a temporary kludge?

The fortran frontend also sets DECL_ARTIFICIAL on variables not mentioned in the source.

Independent of intent, it should not be a long-term solution. The use of DECL_ARTIFICIAL you describe is clearly correct, according to both the documentation and long-standing practice. The only part of the compiler that should pay attention to DECL_ARTIFICIAL is probably the debug generators.

--
Mark Mitchell
CodeSourcery, LLC
(916) 791-8304
mark@codesourcery.com

References:
- Re: Question on GIMPLE semantics and EH
  - From: Richard Kenner
- Re: Question on GIMPLE semantics and EH
  - From: Paul Brook

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]