Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
M
mu-impl-fast
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
40
Issues
40
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
mu
mu-impl-fast
Commits
d851145b
Commit
d851145b
authored
Jun 13, 2017
by
qinsoon
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
[wip] remove reserve arg (we did it twice, so its nop)
parent
a6998089
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
0 additions
and
14 deletions
+0
-14
src/compiler/backend/arch/x86_64/inst_sel.rs
src/compiler/backend/arch/x86_64/inst_sel.rs
+0
-14
No files found.
src/compiler/backend/arch/x86_64/inst_sel.rs
View file @
d851145b
...
...
@@ -3065,25 +3065,11 @@ impl <'a> InstructionSelection {
}
if
!
stack_args
.is_empty
()
{
// deal with stack arg, put them on stack
// in reverse order, i.e. push the rightmost arg first to stack
stack_args
.reverse
();
// "The end of the input argument area shall be aligned on a 16
// (32, if __m256 is passed on stack) byte boundary." - x86 ABI
// if we need to special align the args, we do it now
// (then the args will be put to stack following their regular alignment)
// reserve stack args - we want to layout stack args as below
// RSP -> .............
// (padding)
// (padding)
// RSP -> argN, argN-1, ...
// so we need to layout args in reverse order
stack_args
.reverse
();
let
stack_arg_tys
=
stack_args
.iter
()
.map
(|
x
|
x
.ty
.clone
())
.collect
();
let
(
stack_arg_size
,
_
,
stack_arg_offsets
)
=
BackendType
::
sequential_layout
(
&
stack_arg_tys
,
vm
);
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment