This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran 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: PR40011 -fwhole-file problems

From: Paul Richard Thomas <paul dot richard dot thomas at gmail dot com>
To: Richard Guenther <richard dot guenther at gmail dot com>
Cc: Tobias Schlüter <tobias dot schlueter at physik dot uni-muenchen dot de>, "fortran at gcc dot gnu dot org" <fortran at gcc dot gnu dot org>
Date: Thu, 4 Jun 2009 11:03:35 +0200
Subject: Re: PR40011 -fwhole-file problems
References: <339c37f20906011203r5a98f96fl960ac2589c7f7fe5@mail.gmail.com> <4A245599.4090108@physik.uni-muenchen.de> <84fc9c000906030325j5c9c0f5ek8778cbe040b0de84@mail.gmail.com>

Dear Richard,

Thank you for your response to this - I am very pleased that you
continue to take an interest in gfortran.

> The inliner is perfectly capable of inlining functions with static
> variables. ?Likely GFortran messes up the flags for the static
> vars so they get copied during inlining (which is what you see above,
> use -uid on the dump flag to see the DECL uids).

How does one deal with this?  By putting TREE_STATIC variables in
global scope?  I could not immediately discern from tree.def or tree.h
the sense in which gfortran messes up the flags.

Cheers

Paul

-- 
The knack of flying is learning how to throw yourself at the ground and miss.
       --Hitchhikers Guide to the Galaxy

Follow-Ups:
- Re: PR40011 -fwhole-file problems
  - From: Richard Guenther

References:
- PR40011 -fwhole-file problems
  - From: Paul Richard Thomas
- Re: PR40011 -fwhole-file problems
  - From: Tobias Schlüter
- Re: PR40011 -fwhole-file problems
  - From: Richard Guenther

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