From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: Dave Korn <dave.korn.cygwin@googlemail.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Dw2 CIE no longer contains personality routine augmentation?
Date: Thu, 01 Oct 2009 12:40:00 -0000 [thread overview]
Message-ID: <4AC4A6B1.8070805@gmail.com> (raw)
In-Reply-To: <84fc9c000910010138i2bb4fa1ep5e88a7cda08968af@mail.gmail.com>
Richard Guenther wrote:
> On Thu, Oct 1, 2009 at 2:47 AM, Dave Korn wrote:
>> I'm using g++.old-deja/g++.brendan/new3.C as a testcase to investigate a
>> problem with dllimport at the moment, and noticed something a bit unusual:
>>
>> Here is the CIE data from new3.C as compiled with gcc-4.3.4
>> And now with gcc trunk@152230, I see that the generated CIE no longer has
>> any augmentation, particularly it doesn't point to the personality routine any
>> more:
>> Is this intentional?
>
> Yes. If it doesn't need one it doesn't get one.
Augh! That was actually sooooo useful to me in making sure that my shared
libstdc++ dll got linked into the executable even when all other references
from the exe to the library got shunted aside by --wrap.
Would it be reasonable to disable the optimisation on a target-specific
basis? Either that or I'm going to have invent a modified version of --wrap,
or just shove some other dummy reference to the library into object files
unconditionally. (Actually that might turn out to be as simple as adding a -u
option to the linker command line, so maybe it would even be better. Haven't
tested that yet though.)
cheers,
DaveK
prev parent reply other threads:[~2009-10-01 12:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 0:33 Dave Korn
2009-10-01 8:38 ` Richard Guenther
2009-10-01 12:40 ` Dave Korn [this message]
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=4AC4A6B1.8070805@gmail.com \
--to=dave.korn.cygwin@googlemail.com \
--cc=gcc@gcc.gnu.org \
--cc=richard.guenther@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).