public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/65548] [5/6 Regression] gfc_conv_procedure_call
Date: Fri, 17 Apr 2015 16:31:00 -0000	[thread overview]
Message-ID: <bug-65548-4-knTLpbfY9B@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65548-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65548

--- Comment #18 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> I applied the patch, and did a make in the built folder. I still get the ICE.

Did you do "make install"?

> Or do I have to change the file gcc/fortran/trans-stmt.c and do a completely
> new built of the gcc/gfortran compiler suite?

It is always safer to do a clean bootstrap, but it should not be necessary.
When patching gfortran I usually doe "touch gcc/fortran/*" which forces to
rebuild fortran at all stages and rebuild libgfortran.


  parent reply	other threads:[~2015-04-17 16:31 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25  7:11 [Bug fortran/65548] New: [5.0 " juergen.reuter at desy dot de
2015-03-25  7:15 ` [Bug fortran/65548] " juergen.reuter at desy dot de
2015-03-25  9:03 ` [Bug fortran/65548] [5 " jakub at gcc dot gnu.org
2015-03-25  9:03 ` dominiq at lps dot ens.fr
2015-03-27 13:47 ` dominiq at lps dot ens.fr
2015-04-07 14:11 ` vehre at gcc dot gnu.org
2015-04-09  8:26 ` vehre at gcc dot gnu.org
2015-04-10  7:19 ` juergen.reuter at desy dot de
2015-04-10 13:48 ` dominiq at lps dot ens.fr
2015-04-10 13:50 ` juergen.reuter at desy dot de
2015-04-10 16:48 ` juergen.reuter at desy dot de
2015-04-15 10:06 ` [Bug fortran/65548] [5/6 " vehre at gcc dot gnu.org
2015-04-15 12:48 ` juergen.reuter at desy dot de
2015-04-15 13:03 ` dominiq at lps dot ens.fr
2015-04-17 16:17 ` juergen.reuter at desy dot de
2015-04-17 16:31 ` dominiq at lps dot ens.fr [this message]
2015-04-22 12:02 ` jakub at gcc dot gnu.org
2015-04-23 12:51 ` vehre at gcc dot gnu.org
2015-04-23 12:54 ` juergen.reuter at desy dot de
2015-04-23 13:02 ` juergen.reuter at desy dot de
2015-04-23 13:22 ` dominiq at lps dot ens.fr
2015-04-23 13:52 ` juergen.reuter at desy dot de
2015-04-23 15:06 ` juergen.reuter at desy dot de
2015-04-23 15:11 ` dominiq at lps dot ens.fr
2015-04-28 21:55 ` vehre at gcc dot gnu.org
2015-04-28 22:40 ` juergen.reuter at desy dot de
2015-04-29  8:01 ` vehre at gcc dot gnu.org
2015-04-29  8:06 ` juergen.reuter at desy dot de
2015-04-29  8:33 ` vehre at gcc dot gnu.org
2015-04-29 13:19 ` juergen.reuter at desy dot de
2015-05-05  9:12 ` vehre at gcc dot gnu.org
2015-05-05  9:36 ` juergen.reuter at desy dot de
2015-05-05 10:15 ` vehre at gcc dot gnu.org
2015-05-05 12:43 ` juergen.reuter at desy dot de
2015-05-20 14:57 ` vehre at gcc dot gnu.org
2015-05-29  9:06 ` vehre at gcc dot gnu.org

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-65548-4-knTLpbfY9B@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).