From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Hei Chan <structurechart@yahoo.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: Expected Behavior in Mixing -std=c++0x and default std?
Date: Tue, 08 Apr 2014 14:31:00 -0000 [thread overview]
Message-ID: <CAH6eHdQcEuPYv0zdQtZ2cxC_f6G3UBgJrVDgpQ_eSrvWAfyEvQ@mail.gmail.com> (raw)
In-Reply-To: <1396944400.37620.YahooMailNeo@web165001.mail.bf1.yahoo.com>
On 8 April 2014 09:06, Hei Chan wrote:
> Hi,
>
> If I have a static library A that builds with default std with another header only library B, and then my program links library A and uses some classes in library B with -std=c++0x. Will this usage create any issue?
>
> I am running into an issue that one of the member variables in library B (boost ASIO to be precise) has a different memory address (only off by 4 bytes) over time.
>
> Any input is welcome.
>
> Thanks in advance.
>
>
> Cheers,
> Hei
> P.S. I am using GCC 4.6.x on CentOS 6.5.
With GCC 4.6.x, 4.7.2 or 4.8.x that should work OK. With GCC 4.7.0 or
4.7.1 there would be a problem if B uses std::list.
You should be able to find why the offset of the ASIO type changed, it
might not be due to a std::lib type.
next prev parent reply other threads:[~2014-04-08 14:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 8:06 Hei Chan
2014-04-08 14:31 ` Jonathan Wakely [this message]
2014-04-08 22:44 ` Hei Chan
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=CAH6eHdQcEuPYv0zdQtZ2cxC_f6G3UBgJrVDgpQ_eSrvWAfyEvQ@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=structurechart@yahoo.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).