public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bkoz at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/37520] junk `(,%eax,4)' after expression / suffix or operands invalid for `lea' for libstdc++ deque/init-list.cc
Date: Mon, 05 Jan 2009 20:23:00 -0000	[thread overview]
Message-ID: <20090105202307.10022.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37520-231@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from bkoz at gcc dot gnu dot org  2009-01-05 20:23 -------

The other kind of freebsd6.3 fail in libstdc++ is:

testsuite/25_algorithms/max/3.cc

/sw/test/GCC/trunk/libstdc++-v3/testsuite/25_algorithms/max/3.cc:26: undefined
reference to `_47'

/var/tmp//ccInT4La.o(.text._Z6test01v+0xb):/sw/test/GCC/trunk/libstdc++-v3/testsuite/25_algorithms/max/3.cc:26:
undefined reference to `_47'


On linux I see these in the linked binary:

0000000000600b58 d ._65
0000000000600b64 d ._66
0000000000600b70 d ._67
0000000000600b7c d ._68
0000000000600b88 d ._69
0000000000600b94 d ._70

So assuming this would be ._48 or '.' used instead of '$'. Does BSD already
define NO_DOT_IN_LABEL? Although I am not quite sure what is going on it
appears as if the freebsd config (and or assember) for correct linking of some
of these C++ entities is off.

Anyway. I thought NO_DOT_IN_LABEL/NO_DOLLAR_IN_LABEL will change the name of
exported symbols and is ABI-breaking.

IMHO figuring this out before the 4.4.0 release seems advisable. 


-- 


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


  parent reply	other threads:[~2009-01-05 20:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-14 20:47 [Bug target/37520] New: " gerald at pfeifer dot com
2008-09-14 20:48 ` [Bug target/37520] " gerald at pfeifer dot com
2008-09-14 20:49 ` gerald at pfeifer dot com
2008-09-14 22:25 ` pinskia at gcc dot gnu dot org
2008-09-15  9:02 ` ubizjak at gmail dot com
2008-09-21 10:16 ` gerald at pfeifer dot com
2009-01-05 20:02 ` bkoz at gcc dot gnu dot org
2009-01-05 20:23 ` bkoz at gcc dot gnu dot org [this message]
2009-02-02 18:26 ` bkoz at gcc dot gnu dot org
2009-02-24 17:56 ` [Bug target/37520] [4.4 Regression] " bkoz at gcc dot gnu dot org
2009-02-25  7:33 ` ubizjak at gmail dot com
2009-02-25  8:57 ` rguenth at gcc dot gnu dot org
2009-03-01 13:03 ` gerald at pfeifer dot com
2009-03-01 19:16 ` ubizjak at gmail dot com
2009-03-01 20:13 ` ubizjak at gmail dot com
2009-03-01 20:20 ` hjl dot tools at gmail dot com
2009-03-01 20:23 ` hjl dot tools at gmail dot com
2009-03-01 20:40 ` [Bug target/37520] NO_DOLLAR_IN_LABEL doesn't work on FreeBSD/x86 hjl dot tools at gmail dot com
2009-03-01 21:54 ` [Bug target/37520] Undefine " hjl dot tools at gmail dot com
2009-03-02  3:20 ` [Bug target/37520] NO_DOLLAR_IN_LABEL should be defined on x86 targets hjl dot tools at gmail dot com
2009-03-02 10:08 ` rguenth at gcc dot gnu dot org
2009-03-07  1:47 ` hjl at gcc dot gnu dot org
2009-03-07  1:48 ` hjl dot tools at gmail 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=20090105202307.10022.qmail@sourceware.org \
    --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).