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 lto/56168] [4.8 Regression] GCC seems to disregard -fno-builtin when compiling with LTO
Date: Fri, 01 Feb 2013 09:42:00 -0000	[thread overview]
Message-ID: <bug-56168-4-RhfFwkSxQs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56168-4@http.gcc.gnu.org/bugzilla/>


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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2013-02-01
         AssignedTo|unassigned at gcc dot       |rguenth at gcc dot gnu.org
                   |gnu.org                     |
   Target Milestone|---                         |4.8.0
     Ever Confirmed|0                           |1

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> 2013-02-01 09:42:36 UTC ---
-f[no-]builtin-* is a frontend option not supported by LTO (nor by Fortran
for example).  That it controls also middle-end behavior with respect to
LTO streaming 'pow' as a builtin is a bug I suppose (to be analyzed).
Probably caused by

      /* For variables prefer the builtin if one is available.  */
      else if (TREE_CODE (prevailing->symbol.decl) == FUNCTION_DECL)
        {
          for (e = first; e; e = e->symbol.next_sharing_asm_name)
            if (TREE_CODE (e->symbol.decl) == FUNCTION_DECL
                && DECL_BUILT_IN (e->symbol.decl))
              {
                prevailing = e;
                break;
              }
        }

and LTO un-conditionally initializing all builtins (well, and that's needed
unless we can do that lazily during streaming as we stream builtin decls
by their DECL_FUNCTION_CODE ...).

Hm.  I'll have a looksee.


  reply	other threads:[~2013-02-01  9:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01  2:44 [Bug lto/56168] New: " d.g.gorbachev at gmail dot com
2013-02-01  9:42 ` rguenth at gcc dot gnu.org [this message]
2013-02-01 12:35 ` [Bug lto/56168] " rguenth at gcc dot gnu.org
2013-02-01 12:40 ` rguenth at gcc dot gnu.org
2013-02-04 12:20 ` rguenth at gcc dot gnu.org
2013-02-04 12:20 ` rguenth 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-56168-4-RhfFwkSxQs@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).