public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/10980] vararg functions are not inlined
Date: Tue, 18 Oct 2011 09:54:00 -0000	[thread overview]
Message-ID: <bug-10980-4-kpSy9pessj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-10980-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-10-18 09:54:03 UTC ---
(In reply to comment #11)
> (In reply to comment #10)
> > I bet it just ignores the attribute that is not how the attribute is
> > supposed to work.
> > 
> > We output error in this case intentionally (and warning in at the same
> > spot if function is declared inline and -Winline is given).
> > Functions marked always_inlined really ought to be always inlined and
> > attribute is supposed to be useable in the cases where compilation would
> > fail otherwise (such as SSE buitins).
> > 
> > Our documentation is however not particularly clear here, perhaps it should
> > be updated...
> > 
> > Honza
> 
> Seeing that documentation is unclear (no mention of when errors or warnings are
> produced), and Qt Creator devs want to know what version of GCC started
> errorring on this, could you please let me know what GCC version started
> producing errors? Thanks!

GCC always errored out on this (previously by sorry(), now with error()).

We can possibly inline varargs functions when we delay lowering the
vararg builtins to the stdarg pass (which would clean up its implementation
a lot ...).


  parent reply	other threads:[~2011-10-18  9:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-10980-4@http.gcc.gnu.org/bugzilla/>
2011-09-23 13:47 ` vanboxem.ruben at gmail dot com
2011-09-23 13:59 ` hubicka at ucw dot cz
2011-09-23 14:10 ` vanboxem.ruben at gmail dot com
2011-09-23 14:21   ` Jan Hubicka
2011-09-23 14:32 ` hubicka at ucw dot cz
2011-10-17 18:45 ` vanboxem.ruben at gmail dot com
2011-10-18  9:54 ` rguenth at gcc dot gnu.org [this message]
2021-09-06  6:50 ` pinskia 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-10980-4-kpSy9pessj@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).