public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/10980] vararg functions are not inlined
Date: Fri, 23 Sep 2011 13:59:00 -0000	[thread overview]
Message-ID: <bug-10980-4-qz0IMCxiul@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 #8 from Jan Hubicka <hubicka at ucw dot cz> 2011-09-23 13:40:55 UTC ---
> This problem popped up when compiling LLVM's libc++:
> M:\Development\Source\libc++\src\locale.cpp:1:0: warning: -fPIC ignored for
> target (all code is position independent) [enabled by default]
> M:\Development\Source\libc++\include/locale: In function 'int
> std::__1::__asprintf_l(char**, _locale_t, const char*, ...)':
> M:\Development\Source\libc++\include/locale:372:5: sorry, unimplemented:
> function 'int std::__1::__asprintf_l(char**, _locale_t, const char*, ...)' can
> never be inlined because it uses variable argument lists
> M:\Development\Source\libc++\include/locale: In function 'int
> std::__1::__sprintf_l(char*, _locale_t, const char*, ...)':

It seems wrong to add always_inline attribute on something like this.  I am not
aware
that LLVM would be inlining variadic function either
(even though it is doable in some trivial cases)

Honza


  parent reply	other threads:[~2011-09-23 13:42 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 [this message]
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
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-qz0IMCxiul@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).