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 middle-end/60235] Inlining fails with template specialization and -fPIC on Linux AMD64
Date: Mon, 17 Feb 2014 12:37:00 -0000	[thread overview]
Message-ID: <bug-60235-4-euyIFis07y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60235-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #2)
> The specialization is a regular function, not comdat, thus it is not
> appropriate to inline it at -O2 -fpic, only -O3 is inlining functions
> regardless to whether they could be interposed or not,

Wouldn't that be a wrong-code bug though?

> or for -O2 without
> -fpic because the symbol can't be interposed.  Or use the inline keyword for
> the specialization.


  parent reply	other threads:[~2014-02-17 12:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-17  6:27 [Bug middle-end/60235] New: " joker.eph at gmail dot com
2014-02-17  6:27 ` [Bug middle-end/60235] " joker.eph at gmail dot com
2014-02-17  8:15 ` jakub at gcc dot gnu.org
2014-02-17 12:37 ` rguenth at gcc dot gnu.org [this message]
2014-02-17 17:05 ` hubicka at gcc dot gnu.org
2014-02-17 17:28 ` joker.eph at gmail dot com
2014-02-17 18:59 ` jakub at gcc dot gnu.org
2014-02-17 19:03 ` joker.eph at gmail dot com
2022-01-10 10:07 ` [Bug ipa/60235] " pinskia at gcc dot gnu.org
2022-01-10 10:08 ` 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-60235-4-euyIFis07y@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).