Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
GHC
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Alexis King
GHC
Commits
0f1041d2
Commit
0f1041d2
authored
25 years ago
by
Reuben Thomas
Browse files
Options
Downloads
Patches
Plain Diff
[project @ 2000-06-27 13:45:30 by rrt]
Some initial notes on DLLs. plsmrg
parent
57ff175e
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
ghc/compiler/DLL-NOTES
+58
-0
58 additions, 0 deletions
ghc/compiler/DLL-NOTES
with
58 additions
and
0 deletions
ghc/compiler/DLL-NOTES
0 → 100644
+
58
−
0
View file @
0f1041d2
The DLL story
-------------
***
This file is intended to be a focal point for notes on how DLLs work. Please
add cross-references to source and other docs, especially when you don't
find something here that you need.
***
Introduction
------------
On Windows, DLLs are synonymous with packages (since 4.07; this change
simplified a rather horrible mess). Hence whenever a module is to be
compiled to go in a DLL, it must be compiled with -package-name dll-name.
Typically, failing to do this gives Windows error message boxes of the form
"The instruction at address <x> tried to read memory at address <x>".
Dependencies
------------
Because references in DLLs must be fully resolved when the DLL is compiled
(except for references to other DLLs), it is not possible for DLLs to call
the main program. This means that the parts of the RTS and standard package
which call the main program cannot be compiled into the relevant DLLs, and
must instead be compiled as standalone object files and linked in to each
executable. This gives the following picture of dependencies within a program:
___________ ___________
| |------>| | GHC-land | Application-land
DLL-land | HSrts.dll | | HSstd.dll | |
|___________|<------|___________| |
| ^ |
-----------------|-------------------|-------------------|
_____v_____ _____|______ |
.o-land | | | | |
| Main.o | | PrelMain.o |-----------------------
|___________| |____________| | |
| | ______v______
| | | |
------------------------------------------>| Main.o |
| |_____________|
(The application's dependencies are not shown.)
Bits of the compiler that deal with DLLs
----------------------------------------
basicTypes/Module.lhs is the most important place, as it deals with which
modules identifiers are in.
basicTypes/name.lhs, other bits of basicTypes/, nativeGen/, codeGen/,
abcCSyn/, and even profiling/ have other references.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment