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
b6f01001
Commit
b6f01001
authored
Jul 28, 1993
by
Richard Stallman
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
(expand_expr, case ADDR_EXPR): Treat CONCAT like REG.
From-SVN: r5030
parent
7f3d4b2f
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
1 deletions
+5
-1
gcc/expr.c
+5
-1
No files found.
gcc/expr.c
View file @
b6f01001
...
...
@@ -5369,7 +5369,11 @@ expand_expr (exp, target, tmode, modifier)
op0
=
force_const_mem
(
TYPE_MODE
(
TREE_TYPE
(
TREE_OPERAND
(
exp
,
0
))),
op0
);
if
(
GET_CODE
(
op0
)
==
REG
||
GET_CODE
(
op0
)
==
SUBREG
)
/* These cases happen in Fortran. Is that legitimate?
Should Fortran work in another way?
Do they happen in C? */
if
(
GET_CODE
(
op0
)
==
REG
||
GET_CODE
(
op0
)
==
SUBREG
||
GET_CODE
(
op0
)
==
CONCAT
)
{
/* If this object is in a register, it must be not
be BLKmode. */
...
...
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