public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dongsheng.song at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/57120] Plain C link with libgcc_s_sjlj-1.dll which not needed
Date: Tue, 30 Apr 2013 10:52:00 -0000 [thread overview]
Message-ID: <bug-57120-4-LZn8lryC0I@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57120-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57120
Dongsheng Song <dongsheng.song at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |
--- Comment #2 from Dongsheng Song <dongsheng.song at gmail dot com> 2013-04-30 10:52:52 UTC ---
(In reply to comment #1)
> No this change wasn't hastily nor wrong. Actual the change makes things
> compliant to logic already used for cygwin for years. Additional it fixed a
> quirk there was about eh-code sometimes not using shared version, if it actual
> was necessary to.
> The point is, if you want to avoid dependency to DLL libgcc version, then
> please use support static option for it. Otherwise you might get dependencies
> to the shared version, and there is nothing wrong about that.
>
> I admit that some functions might be added to shared version, which would be
> for pe-coff better be placed into the pure static part of libgcc. But well
> that is an enhancment issue and not a bug.
It's a regress to gcc 4.7, it't it ?
next prev parent reply other threads:[~2013-04-30 10:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 1:47 [Bug c/57120] New: " dongsheng.song at gmail dot com
2013-04-30 10:42 ` [Bug target/57120] " ktietz at gcc dot gnu.org
2013-04-30 10:52 ` dongsheng.song at gmail dot com [this message]
2013-04-30 11:03 ` ktietz at gcc dot gnu.org
2013-04-30 11:53 ` dongsheng.song at gmail dot com
2013-04-30 13:34 ` ktietz 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-57120-4-LZn8lryC0I@http.gcc.gnu.org/bugzilla/ \
--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).