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
c6b3f1f2
Commit
c6b3f1f2
authored
May 03, 1993
by
Jim Wilson
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
(make_extraction): Move BYTES_BIG_ENDIAN != BITS_BIG_ENDIAN offset
correction after the offset calculation. From-SVN: r4315
parent
50e65854
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
6 deletions
+6
-6
gcc/combine.c
+6
-6
No files found.
gcc/combine.c
View file @
c6b3f1f2
...
...
@@ -4881,12 +4881,6 @@ make_extraction (mode, inner, pos, pos_rtx, len,
endian in both bits and bytes or little endian in bits and bytes.
If it is mixed, we must adjust. */
#if BYTES_BIG_ENDIAN != BITS_BIG_ENDIAN
if
(
!
spans_byte
&&
is_mode
!=
wanted_mem_mode
)
offset
=
(
GET_MODE_SIZE
(
is_mode
)
-
GET_MODE_SIZE
(
wanted_mem_mode
)
-
offset
);
#endif
/* If bytes are big endian and we had a paradoxical SUBREG, we must
adjust OFFSET to compensate. */
#if BYTES_BIG_ENDIAN
...
...
@@ -4902,6 +4896,12 @@ make_extraction (mode, inner, pos, pos_rtx, len,
pos
%=
GET_MODE_BITSIZE
(
wanted_mem_mode
);
}
#if BYTES_BIG_ENDIAN != BITS_BIG_ENDIAN
if
(
!
spans_byte
&&
is_mode
!=
wanted_mem_mode
)
offset
=
(
GET_MODE_SIZE
(
is_mode
)
-
GET_MODE_SIZE
(
wanted_mem_mode
)
-
offset
);
#endif
if
(
offset
!=
0
||
inner_mode
!=
wanted_mem_mode
)
{
rtx
newmem
=
gen_rtx
(
MEM
,
wanted_mem_mode
,
...
...
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