From: Tobias Burnus <burnus@net-b.de>
To: Paul Richard Thomas <paul.richard.thomas@gmail.com>
Cc: "Dominique d'Humières" <dominiq@lps.ens.fr>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>,
"FX Coudert" <fxcoudert@gmail.com>
Subject: Re: [Patch, Fortran] Fix previous patch
Date: Thu, 08 Jan 2015 18:10:00 -0000 [thread overview]
Message-ID: <54AEC7F8.9060005@net-b.de> (raw)
In-Reply-To: <CAGkQGi+MJhuQCGyvVE-Qw9qZ6AcXBN1b62+Ky=adJO7iEKAxDA@mail.gmail.com>
Paul Richard Thomas wrote:
> It looks to me as if you had to do a fair amount of detective work
> there! The patch is OK for trunk.
Thanks for the review - which didn't make it to mailing list for some
reasons (text+HTML email?).
Committed as Rev. 219354
Tobias
> Thanks for your efforts
>
> Paul
>
> On 7 January 2015 at 22:37, Tobias Burnus <burnus@net-b.de
> <mailto:burnus@net-b.de>> wrote:
>
> Early PING: https://gcc.gnu.org/ml/gcc-patches/2015-01/msg00090.html
>
> Tobias Burnus wrote:
>
> Attached is a regtested patch, which fixes the issue.
> Additionally, the variable visibility (TREE_PUBLIC) is now
> depending on the private attribute (copied from the module var
> generation) and I mark the tree as DECL_NONALIASED. The former
> I also did for proc-pointers, which is an unrelated patch.
>
> Build and regtested on x86-64-gnu-linux.
> OK for the trunk?
>
>
> Dominique d'Humières wrote:
>
> Compilation with the new patch fails with
> ../../work/gcc/fortran/trans-decl.c: In function 'void
> gfc_build_qualified_array(tree, gfc_symbol*)':
> ../../work/gcc/fortran/trans-decl.c:855:25: error:
> 'cur_module' was not declared in this scope
> gfc_module_add_decl (cur_module, token);
>
>
> Which shows that w/o compiling and testing, one (usually)
> cannot write patches. Solution is to move the declaration up
> in the file. However, it turned out that that's not
> sufficient: the pushdecl is required.
>
> Tobias
>
> Le 3 janv. 2015 Ã 23:30, Tobias Burnus
> <burnus@net-b.de <mailto:burnus@net-b.de>> a écrit :
>
> Dominique d'Humières wrote:
>
> From a quick test, with the patch I still see the
> error with -m32
>
> It helps if one actually adds the decl. The following
> (still untested) should help. I also marked the token
> as nonaliasing (it really should!) and added for proc
> pointers the tree-public optimization.
>
> Tobias
> <foo.diff>
>
>
>
>
>
>
>
> --
> Outside of a dog, a book is a man's best friend. Inside of a dog it's
> too dark to read.
>
> Groucho Marx
prev parent reply other threads:[~2015-01-08 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-03 10:22 [Patch, Fortran + Testsuite] Fix coarray handling in modules Dominique Dhumieres
2015-01-03 20:50 ` Tobias Burnus
2015-01-03 21:48 ` Dominique d'Humières
2015-01-03 22:30 ` Tobias Burnus
2015-01-03 23:04 ` Dominique d'Humières
2015-01-04 18:58 ` [Patch, Fortran] Fix previous patch (was: Re: [Patch, Fortran + Testsuite] Fix coarray handling in modules) Tobias Burnus
2015-01-04 21:28 ` Dominique d'Humières
2015-01-07 21:37 ` [Patch, Fortran] Fix previous patch Tobias Burnus
[not found] ` <CAGkQGi+MJhuQCGyvVE-Qw9qZ6AcXBN1b62+Ky=adJO7iEKAxDA@mail.gmail.com>
2015-01-08 18:10 ` Tobias Burnus [this message]
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=54AEC7F8.9060005@net-b.de \
--to=burnus@net-b.de \
--cc=dominiq@lps.ens.fr \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=paul.richard.thomas@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).