public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug mi/23042] typedef resolution traverses all CUs for MI var-create
Date: Thu, 28 May 2020 07:51:47 +0000	[thread overview]
Message-ID: <bug-23042-4717-t1afnDhfJe@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23042-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=23042

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vries at gcc dot gnu.org

--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Martin Richtarsky from comment #1)
> Created attachment 10937 [details]
> Reproducer

The GOLD_PATH thing in the script doesn't work for me (and I'm not sure how
it's supposed to work).  I've managed to make it work using -fuse-ld=gold:
...
$ cat build.sh
#!/bin/sh

OPTS="-g -gdwarf-4 -gsplit-dwarf -g2 -ggdb "
LOPTS="-fuse-ld=gold -Wl,--gdb-index"
g++ -c sharedlib.cpp $OPTS -o sharedlib.o
g++ $LOPTS -shared sharedlib.o $OPTS -o libsharedlib.so
g++ -c main.cpp $OPTS -o main.o
g++ $LOPTS -o main $OPTS main.o -L. -lsharedlib
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

       reply	other threads:[~2020-05-28  7:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-23042-4717@http.sourceware.org/bugzilla/>
2020-05-28  7:51 ` vries at gcc dot gnu.org [this message]
2020-05-28 10:43 ` vries at gcc dot gnu.org
2020-05-28 11:40 ` vries 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-23042-4717-t1afnDhfJe@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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).