From: Agner Fog <agner@agner.org>
To: cygwin@cygwin.com
Subject: Re: Clang is using the wrong memory model
Date: Sun, 18 Aug 2019 18:14:00 -0000 [thread overview]
Message-ID: <f2852c05-4f0b-9587-2c4c-bf37485b7455@agner.org> (raw)
In-Reply-To: <20190818115739.GD11632@calimero.vinschen.de>
On 18/08/2019 13.57, Corinna Vinschen wrote:
> Nope, Cygwin uses the Windows loader.
Then, how do you do the extra linking? What is producing the "Cygwin
runtime failure" message when loading/linking a DLL fails?
> If the medium model is wasteful in clang, that's a clang
> optimization problem, not a Cygwin problem.
The medium model in Clang is not wasteful. It does exactly what it is
designed to do. It was never designed with Cygwin in mind. The program
build with a medium model is wasteful because it makes all addresses 64
bits when few or no addresses actually need to be 64 bits.
> If you want to use the small model in your own projects, great, if it
> works for you.
It is not for my own project. I am writing manuals on how to optimize
software.
Agner
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-08-18 16:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1436640898.268382790.1565602671940.JavaMail.root@zimbra54-e10.priv.proxad.net>
2019-08-12 9:45 ` Inefficient use of 64-bit addresses in Clang falk.tannhauser
2019-08-14 5:51 ` Agner Fog
2019-08-16 6:06 ` Clang is using the wrong memory model Agner Fog
2019-08-16 8:25 ` Mark Geisert
2019-08-16 8:26 ` Corinna Vinschen
2019-08-16 9:27 ` Agner Fog
2019-08-16 9:52 ` Agner Fog
2019-08-16 10:39 ` Corinna Vinschen
2019-08-16 10:50 ` Agner Fog
2019-08-16 11:25 ` Corinna Vinschen
2019-08-16 13:28 ` Kai Tietz
2019-08-17 6:59 ` Agner Fog
2019-08-17 9:48 ` Corinna Vinschen
2019-08-18 11:37 ` Agner Fog
2019-08-18 11:58 ` Corinna Vinschen
2019-08-18 18:14 ` Agner Fog [this message]
2019-08-19 8:58 ` Corinna Vinschen
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=f2852c05-4f0b-9587-2c4c-bf37485b7455@agner.org \
--to=agner@agner.org \
--cc=cygwin@cygwin.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).