Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
R
riscv-gcc-1
Overview
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
lvzhengyang
riscv-gcc-1
Commits
477efd50
Commit
477efd50
authored
Apr 25, 1996
by
Richard Kenner
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
(expand_builtin, case BUILT_IN_SETJMP): CLOBBER the static chain after
label at setjmp point. From-SVN: r11886
parent
5c7ad97f
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
0 deletions
+4
-0
gcc/expr.c
+4
-0
No files found.
gcc/expr.c
View file @
477efd50
...
@@ -8593,6 +8593,10 @@ expand_builtin (exp, target, subtarget, mode, ignore)
...
@@ -8593,6 +8593,10 @@ expand_builtin (exp, target, subtarget, mode, ignore)
make sure it's marked as used by this function. */
make sure it's marked as used by this function. */
emit_insn
(
gen_rtx
(
USE
,
VOIDmode
,
hard_frame_pointer_rtx
));
emit_insn
(
gen_rtx
(
USE
,
VOIDmode
,
hard_frame_pointer_rtx
));
/* Mark the static chain as clobbered here so life information
doesn't get messed up for it. */
emit_insn
(
gen_rtx
(
CLOBBER
,
VOIDmode
,
static_chain_rtx
));
/* Now put in the code to restore the frame pointer, and argument
/* Now put in the code to restore the frame pointer, and argument
pointer, if needed. The code below is from expand_end_bindings
pointer, if needed. The code below is from expand_end_bindings
in stmt.c; see detailed documentation there. */
in stmt.c; see detailed documentation there. */
...
...
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