public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "louis.krupp at zoho dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/52332] Internal compiler error in in gfc_get_symbol_decl
Date: Fri, 02 Oct 2015 09:02:00 -0000 [thread overview]
Message-ID: <bug-52332-4-6HMiXYjQXZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52332-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52332
--- Comment #10 from louis.krupp at zoho dot com ---
Paul,
Fixed in revision 228376.
svn must have noticed that the two test files were executable. I'm not 100%
sure how they got that way; in at least one bug report, pr 52332, the
downloaded test cases are executable, and as I was trimming those files down to
what eventually became test cases, vi preserved those mode bits.
Does "make check-" try to run executable test files as though they were
scripts? If not, then I'm not sure how it matters if they're executable or
not, although I'll admit that the svn:executable property is on the untidy
side. I can see the merits of keeping things tidy as a matter of general
principle.
Anyway, that's fixed, and I've made sure that the one test file I haven't
resubmitted isn't executable.
Louis
---- On Fri, 02 Oct 2015 01:34:11 -0700 pault at gcc dot
gnu.org<gcc-bugzilla@gcc.gnu.org> wrote ----
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52332
>
> --- Comment #9 from Paul Thomas <pault at gcc dot gnu.org> ---
> Louis,
>
> Joost is correct about this - we do not set the testcases as executable.
Could
> you revert that, please?
>
> Thanks
>
> Paul
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
>
prev parent reply other threads:[~2015-10-02 9:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 23:09 [Bug fortran/52332] New: " fmartinez at gmv dot com
2012-02-21 23:47 ` [Bug fortran/52332] " burnus at gcc dot gnu.org
2013-06-10 22:07 ` dominiq at lps dot ens.fr
2015-09-10 9:52 ` dominiq at lps dot ens.fr
2015-09-10 9:54 ` dominiq at lps dot ens.fr
2015-10-02 4:04 ` lkrupp at gcc dot gnu.org
2015-10-02 6:01 ` Joost.VandeVondele at mat dot ethz.ch
2015-10-02 8:31 ` pault at gcc dot gnu.org
2015-10-02 8:34 ` pault at gcc dot gnu.org
2015-10-02 9:02 ` louis.krupp at zoho dot com [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=bug-52332-4-6HMiXYjQXZ@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).