From: Oleg Smolsky <osmolsky@netskope.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: [EXTERNAL] Re: Linking issue when mixing GCC10/GCC11 artifacts
Date: Tue, 29 Jun 2021 08:42:49 -0700 [thread overview]
Message-ID: <CAAucFJe1u7TH7rgQ4=kp=kP-MaSm_c+MDpUnOydA5t_B7jxv7g@mail.gmail.com> (raw)
In-Reply-To: <CAAucFJck7_=mvvt4ekQ9RuHT6XB++CHtxDDgK=7q5jB3SFrnwQ@mail.gmail.com>
On Tue, Jun 29, 2021 at 8:39 AM Oleg Smolsky <osmolsky@netskope.com> wrote:
> I am using `g++` to link in both working and failing cases.
>
The peculiar thing is that the linking issue goes away when I change the
reproducer slightly: avoid linking the gcc10-built lib or avoid using
std::unordered_map. Either thing is OK by itself...
next prev parent reply other threads:[~2021-06-29 15:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 4:55 Oleg Smolsky
2021-06-29 5:32 ` Jonathan Wakely
2021-06-29 15:39 ` [EXTERNAL] " Oleg Smolsky
2021-06-29 15:42 ` Oleg Smolsky [this message]
2021-06-29 16:24 ` Oleg Smolsky
2021-06-29 16:40 ` Jonathan Wakely
2021-06-29 16:50 ` Jonathan Wakely
2021-06-29 16:57 ` Oleg Smolsky
2021-06-29 17:22 ` Jonathan Wakely
2021-06-29 23:04 ` Oleg Smolsky
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='CAAucFJe1u7TH7rgQ4=kp=kP-MaSm_c+MDpUnOydA5t_B7jxv7g@mail.gmail.com' \
--to=osmolsky@netskope.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
/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).