public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/14950] [3.4 Regression] [non unit-at-a-time] always_inline does not mix with templates and -O0
Date: Wed, 05 May 2004 20:21:00 -0000	[thread overview]
Message-ID: <20040505202148.20890.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040414064852.14950.veksler@il.ibm.com>


------- Additional Comments From hubicka at gcc dot gnu dot org  2004-05-05 20:21 -------
The problem here is that we do only in order inlining with -fno-unit-at-a-time. 
The C++ frontend is deffering the functions until they are really used so the 
Foo is not passed to cgraph code before main is called and thus it can't be 
inlined. 
I am not sure how to cope with this problem.  (except for fact explaining 
people that using Linux headers definig alwaysinline by default is bad idea). 
Reorganizing C++ frontend to sanely finalize all functions and rely on cgraph 
code to output only needed one is quite drastical step for 3.4.x series (tought 
I definitly can try do it if it sounds sane - it basically means to add flag to 
cgraph code teaching non-unit-at-a-time to not be too active about compiling 
functions that don't seem to be needed and kill the non-unit-at-a-time code in 
the C++ frontend.  If we get lucky, this might work.) 
 
Perhaps we can make always_inline failures warnings in non-unit-at-a-time 
mentioning that alwyas_inline works reliably only in unit-at-a-time? 
 
Concerning the always_inline&Linux kernel isses, perhaps we can either teach 
fixincludes to fix that or do sanity check in the configure erroring out and 
asking user to use glibc includes istead? 
 
Honza 

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mark at codesourcery dot com
         AssignedTo|unassigned at gcc dot gnu   |hubicka at gcc dot gnu dot
                   |dot org                     |org
             Status|NEW                         |ASSIGNED


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


  parent reply	other threads:[~2004-05-05 20:21 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-14  8:06 [Bug c++/14950] New: " veksler at il dot ibm dot com
2004-04-14 11:45 ` [Bug c++/14950] [3.4 Regression] " pinskia at gcc dot gnu dot org
2004-04-21 15:29 ` pinskia at gcc dot gnu dot org
2004-04-22 23:53 ` pinskia at gcc dot gnu dot org
2004-04-23  0:21 ` [Bug c++/14950] [3.4 Regression] [non unit-at-a-time] " pinskia at gcc dot gnu dot org
2004-05-05 20:21 ` hubicka at gcc dot gnu dot org [this message]
2004-05-06  4:10 ` adam at yggdrasil dot com
2004-05-06  6:28 ` adam at yggdrasil dot com
2004-05-06 11:38 ` pinskia at gcc dot gnu dot org
2004-06-22 10:36 ` cvs-commit at gcc dot gnu dot org
2004-06-22 15:39 ` pinskia at gcc dot gnu dot org
2004-10-13 11:23 ` veksler at il dot ibm dot com
2004-10-13 11:34 ` pinskia at gcc dot gnu dot org
2004-10-31  2:43 ` mmitchel at gcc dot gnu dot org
2005-01-26 16:22 ` jeanmichel dot gilbert at videotron dot ca
2005-01-26 16:24 ` jeanmichel dot gilbert at videotron dot ca
2005-02-12 23:18 ` pinskia at gcc dot gnu dot org
2005-02-12 23:19 ` pinskia at gcc dot gnu dot org
2005-03-02  6:53 ` pinskia at gcc dot gnu dot org
2005-03-06 15:10 ` pinskia at gcc dot gnu dot org
2005-05-19 17:39 ` mmitchel at gcc dot gnu dot org
2005-08-22 20:55 ` pinskia at gcc dot gnu dot org
     [not found] <bug-14950-2544@http.gcc.gnu.org/bugzilla/>
2005-10-07  3:17 ` gdr at gcc dot gnu dot org
2006-01-22  3:00 ` gdr at gcc dot gnu dot org
2006-01-22  3:13 ` gdr 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=20040505202148.20890.qmail@sources.redhat.com \
    --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).