public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aoliva at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/53359] [4.8 regression] undefined reference to `__gnu_cxx::__numeric_traits_integer<int>::__min'
Date: Sat, 15 Dec 2012 18:41:00 -0000	[thread overview]
Message-ID: <bug-53359-4-Z2jDAJ4Ets@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53359-4@http.gcc.gnu.org/bugzilla/>


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

Alexandre Oliva <aoliva at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2012-12-15
     Ever Confirmed|0                           |1

--- Comment #7 from Alexandre Oliva <aoliva at gcc dot gnu.org> 2012-12-15 18:40:39 UTC ---
Thanks.  It's not the same issue, after all.  These decls are recorded in
deferred_static_decls, and mudflap_finish_file emits calls to mf_register for
them, so they end up referenced in the toc.  I suppose mudflap_finish_file
needs tweaking to tell that GCC decided not to emit the symbol after all.


  parent reply	other threads:[~2012-12-15 18:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15 10:12 [Bug target/53359] New: " schwab@linux-m68k.org
2012-05-15 17:43 ` [Bug target/53359] " schwab@linux-m68k.org
2012-05-16 10:33 ` rguenth at gcc dot gnu.org
2012-05-16 12:47 ` hubicka at gcc dot gnu.org
2012-05-16 13:25 ` schwab@linux-m68k.org
2012-05-16 13:36 ` schwab@linux-m68k.org
2012-09-07 12:01 ` rguenth at gcc dot gnu.org
2012-12-06 21:40 ` aoliva at gcc dot gnu.org
2012-12-07  0:02 ` schwab@linux-m68k.org
2012-12-15 18:41 ` aoliva at gcc dot gnu.org [this message]
2012-12-15 19:04 ` [Bug libmudflap/53359] " aoliva at gcc dot gnu.org
2013-01-18 11:00 ` aoliva at gcc dot gnu.org
2013-01-18 11:18 ` aoliva 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-53359-4-Z2jDAJ4Ets@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).