public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "espindola at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/40459] g++.dg/abi/mangle*.C fail on darwin
Date: Thu, 17 Dec 2009 18:09:00 -0000	[thread overview]
Message-ID: <20091217180947.21792.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40459-12313@http.gcc.gnu.org/bugzilla/>



------- Comment #10 from espindola at gcc dot gnu dot org  2009-12-17 18:09 -------
I tried to build gcc on darwin to debug this but the build fails with a link
failure (sorry, don't remember exactly where). Do I need to do something
special to build on darwin?

The error message is emitted when mangling the names and the "instantiated
from" bits use input_location. Yes, that is bad :-(

I assume that the difference is coming from use computing the assembler name at
a different point in time when building on darwin.

The short term "fix" might be to force the assembler name computation to happen
at a fixed point in time for both darwin and non-darwin systems.

The correct fix would be to not use input_location.


-- 

espindola at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dnovillo at gcc dot gnu dot
                   |                            |org
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2009-12-17 18:09:47
               date|                            |


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


  parent reply	other threads:[~2009-12-17 18:09 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16 12:48 [Bug testsuite/40459] New: " dominiq at lps dot ens dot fr
2009-07-20  3:08 ` [Bug testsuite/40459] " howarth at nitro dot med dot uc dot edu
2009-07-27 14:02 ` howarth at nitro dot med dot uc dot edu
2009-09-27  3:43 ` howarth at nitro dot med dot uc dot edu
2009-12-15  1:56 ` howarth at nitro dot med dot uc dot edu
2009-12-16 13:59 ` howarth at nitro dot med dot uc dot edu
2009-12-16 14:12 ` jason at gcc dot gnu dot org
2009-12-16 14:32 ` howarth at nitro dot med dot uc dot edu
2009-12-16 20:29 ` howarth at nitro dot med dot uc dot edu
2009-12-16 22:19 ` howarth at nitro dot med dot uc dot edu
2009-12-17 18:09 ` espindola at gcc dot gnu dot org [this message]
2009-12-17 19:16 ` dominiq at lps dot ens dot fr
2009-12-22 18:29 ` howarth at nitro dot med dot uc dot edu
2010-03-01  0:23 ` mikestump at comcast dot net
2010-03-01 10:20 ` dominiq at lps dot ens dot fr

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=20091217180947.21792.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).