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
5bf6466a
Commit
5bf6466a
authored
28 years ago
by
David Edelsohn
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
prepend underscores to itrunc and uitrunc
define RS6000_MCOUNT macro as symbol with underscores From-SVN: r13906
parent
9c849d2a
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
3 deletions
+6
-3
gcc/config/rs6000/rs6000.h
+6
-3
No files found.
gcc/config/rs6000/rs6000.h
View file @
5bf6466a
...
...
@@ -2209,8 +2209,8 @@ extern int rs6000_trunc_used;
/* Function names to call to do floating point truncation. */
#define RS6000_ITRUNC "itrunc"
#define RS6000_UITRUNC "uitrunc"
#define RS6000_ITRUNC "
__
itrunc"
#define RS6000_UITRUNC "
__
uitrunc"
/* Prefix and suffix to use to saving floating point */
#ifndef SAVE_FP_PREFIX
...
...
@@ -2224,6 +2224,9 @@ extern int rs6000_trunc_used;
#define RESTORE_FP_SUFFIX ""
#endif
/* Function name to call to do profiling. */
#define RS6000_MCOUNT ".__mcount"
/* Control the assembler format that we output. */
...
...
@@ -2262,7 +2265,7 @@ extern int rs6000_trunc_used;
private_data_section (); \
text_section (); \
if (profile_flag) \
fp
uts ("\t.extern .mcount\n", FILE);
\
fp
rintf (FILE, "\t.extern %s\n", RS6000_MCOUNT);
\
rs6000_file_start (FILE, TARGET_CPU_DEFAULT); \
}
...
...
This diff is collapsed.
Click to expand it.
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