public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/20538] compiling -finline-functions -O2 and we crash at runtime
Date: Sat, 19 Mar 2005 13:24:00 -0000	[thread overview]
Message-ID: <20050319132417.4771.qmail@sourceware.org> (raw)
In-Reply-To: <20050318192834.20538.pinskia@gcc.gnu.org>


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-03-19 13:24 -------
(In reply to comment #10)
> (In reply to comment #8)
> 
> > Due to general gfortran lameness only contained functions are ever inlined.  
> > Top-level functions are never inlined.  
> 
> Why?
I think Paul means that the front-end is wrong (and is a bug) in that it will not allow the inlining of top 
level functions.  

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20538


  parent reply	other threads:[~2005-03-19 13:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-18 19:28 [Bug fortran/20538] New: " pinskia at gcc dot gnu dot org
2005-03-18 22:24 ` [Bug fortran/20538] " kargl at gcc dot gnu dot org
2005-03-18 22:36 ` kargl at gcc dot gnu dot org
2005-03-19  0:54 ` tobi at gcc dot gnu dot org
2005-03-19  1:35 ` tobi at gcc dot gnu dot org
2005-03-19  1:42 ` pinskia at gcc dot gnu dot org
2005-03-19  1:47 ` tobi at gcc dot gnu dot org
2005-03-19  1:57 ` tobi at gcc dot gnu dot org
2005-03-19  1:59 ` pbrook at gcc dot gnu dot org
2005-03-19 12:08 ` tobi at gcc dot gnu dot org
2005-03-19 13:20 ` Thomas dot Koenig at online dot de
2005-03-19 13:24 ` pinskia at gcc dot gnu dot org [this message]
2005-05-18 21:23 ` tobi at gcc dot gnu dot org
2005-06-04 21:00 ` tobi at gcc dot gnu dot 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=20050319132417.4771.qmail@sourceware.org \
    --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).