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
Model registry
Operate
Terraform modules
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
Gesh
GHC
Commits
4e6a9322
Commit
4e6a9322
authored
27 years ago
by
sof
Browse files
Options
Downloads
Patches
Plain Diff
[project @ 1997-10-05 20:41:52 by sof]
Added (inactive) x86 code for storing away C stack pointer in TSOs reg table
parent
44ffc9c2
Loading
Loading
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
ghc/includes/StgRegs.lh
+14
-0
14 additions, 0 deletions
ghc/includes/StgRegs.lh
with
14 additions
and
0 deletions
ghc/includes/StgRegs.lh
+
14
−
0
View file @
4e6a9322
...
...
@@ -45,6 +45,20 @@ void SaveAllStgRegs(STG_NO_ARGS)
/* CurrentRegTable = BaseReg; */
# endif
#endif
/* Hack!!! slam the current C stack pointer into the reg. table
in the event that we need to copy a chunk of the C stack
before entering Haskell via a stable pointer (contact
<sof> for (gruesome) details!)
Only save this once.
ToDo: support this across platforms.
*/
#if 0 && defined(CONCURRENT) && defined(i386_TARGET_ARCH)
if (CurrentTSO != CurrentTSOinC) {
__asm__ volatile (" mov %%esp,%0" : "m=" (CurrentRegTable->rCstkptr));
}
#endif
#ifdef REG_R1
SAVE_R1 = R1;
...
...
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