public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/60790] libatomic convenience library selects IFUNC implementation before obtaining cpu info.
Date: Wed, 09 Apr 2014 13:32:00 -0000	[thread overview]
Message-ID: <bug-60790-4-kOG6F4cttY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60790-4@http.gcc.gnu.org/bugzilla/>

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

Ian Lance Taylor <ian at airs dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |NEW
   Last reconfirmed|                            |2014-04-09
                 CC|                            |ian at airs dot com
         Resolution|INVALID                     |---
     Ever confirmed|0                           |1

--- Comment #3 from Ian Lance Taylor <ian at airs dot com> ---
Andrew, you are closing this way too fast.  This same problem is going to arise 
whenever libatomic is statically linked.  The library assumes that global
constructors are run before IFUNC selectors, but that is not the case in a
static link.  IFUNC selectors are run first.


  parent reply	other threads:[~2014-04-09 13:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-09  5:19 [Bug go/60790] New: " gary at intrepid dot com
2014-04-09  5:28 ` [Bug go/60790] " gary at intrepid dot com
2014-04-09  5:38 ` [Bug libgcc/60790] " pinskia at gcc dot gnu.org
2014-04-09 13:32 ` ian at airs dot com [this message]
2014-04-09 13:44 ` jakub at gcc dot gnu.org
2014-04-09 15:55 ` gary at intrepid dot com

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-60790-4-kOG6F4cttY@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).