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
cd8998a3
Commit
cd8998a3
authored
Dec 08, 1999
by
Bernd Schmidt
Committed by
Bernd Schmidt
Dec 08, 1999
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Don't hoist volatile mems out of loops.
From-SVN: r30834
parent
dd4be5a1
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
6 additions
and
1 deletions
+6
-1
gcc/ChangeLog
+4
-0
gcc/loop.c
+2
-1
No files found.
gcc/ChangeLog
View file @
cd8998a3
1999
-
12
-
08
Bernd
Schmidt
<
bernds
@cygnus
.
co
.
uk
>
*
loop
.
c
(
insert_loop_mem
)
:
Don
'
t
hoist
volatile
mems
out
of
loops
.
1999
-
12
-
08
Jakub
Jelinek
<
jakub
@redhat
.
com
>
*
config
/
sparc
/
sparc
.
c
(
ultra_cmove_results_ready_p
,
...
...
gcc/loop.c
View file @
cd8998a3
...
...
@@ -9667,7 +9667,8 @@ insert_loop_mem (mem, data)
because we can't put it in a register. We still store it in the
table, though, so that if we see the same address later, but in a
non-BLK mode, we'll not think we can optimize it at that point. */
loop_mems
[
loop_mems_idx
].
optimize
=
(
GET_MODE
(
m
)
!=
BLKmode
);
loop_mems
[
loop_mems_idx
].
optimize
=
(
GET_MODE
(
m
)
!=
BLKmode
&&
!
MEM_VOLATILE_P
(
m
));
loop_mems
[
loop_mems_idx
].
reg
=
NULL_RTX
;
++
loop_mems_idx
;
...
...
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