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
a66a10c7
Commit
a66a10c7
authored
Apr 11, 1993
by
Richard Stallman
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
(can_combine_p): Don't move an UNSPEC_VOLATILE.
From-SVN: r4085
parent
c8cfe1f6
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
2 deletions
+4
-2
gcc/combine.c
+4
-2
No files found.
gcc/combine.c
View file @
a66a10c7
...
...
@@ -825,10 +825,12 @@ can_combine_p (insn, i3, pred, succ, pdest, psrc)
If the insns are adjacent, a use can't cross a set even though we
think it might (this can happen for a sequence of insns each setting
the same destination; reg_last_set of that register might point to
a NOTE). Also, don't move a volatile asm across any other insns. */
a NOTE). Also, don't move a volatile asm or UNSPEC_VOLATILE across
any other insns. */
||
(
!
all_adjacent
&&
(
use_crosses_set_p
(
src
,
INSN_CUID
(
insn
))
||
(
GET_CODE
(
src
)
==
ASM_OPERANDS
&&
MEM_VOLATILE_P
(
src
))))
||
(
GET_CODE
(
src
)
==
ASM_OPERANDS
&&
MEM_VOLATILE_P
(
src
))
||
GET_CODE
(
src
)
==
UNSPEC_VOLATILE
))
/* If there is a REG_NO_CONFLICT note for DEST in I3 or SUCC, we get
better register allocation by not doing the combine. */
||
find_reg_note
(
i3
,
REG_NO_CONFLICT
,
dest
)
...
...
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