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
f18969c0
Commit
f18969c0
authored
Dec 30, 2000
by
Philip Blundell
Committed by
Phil Blundell
Dec 30, 2000
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix typos.
From-SVN: r38562
parent
2df88e9f
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
9 additions
and
2 deletions
+9
-2
gcc/ChangeLog
+6
-0
gcc/config/arm/arm.c
+3
-2
No files found.
gcc/ChangeLog
View file @
f18969c0
2000-12-30 Philip Blundell <philb@gnu.org>
* config/arm/arm.c (arm_expand_prologue): Fix typos in error
message and comment. Note location of testcase for an unhandled
situation.
2000-12-30 Jeffrey Oldham <oldham@codesourcery.com>
* defaults.h (BUILD_VA_LIST_TYPE): New definition.
...
...
gcc/config/arm/arm.c
View file @
f18969c0
...
...
@@ -7736,9 +7736,10 @@ arm_expand_prologue ()
/* FIXME - the way to handle this situation is to allow
the pretend args to be dumped onto the stack, then
reuse r3 to save IP. This would involve moving the
copying o
s
SP into IP until after the pretend args
copying o
f
SP into IP until after the pretend args
have been dumped, but this is not too hard. */
error
(
"Unable to find a temporary location for static chanin register"
);
/* [See e.g. gcc.c-torture/execute/nest-stdar-1.c.] */
error
(
"Unable to find a temporary location for static chain register"
);
}
if
(
fp_offset
)
...
...
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