Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
G
gcc-cobol
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
COBOLworx
gcc-cobol
Commits
b50ccaf6
Commit
b50ccaf6
authored
3 years ago
by
Jeff Law
Browse files
Options
Downloads
Patches
Plain Diff
Make bfin-elf build again
gcc/ * config/bfin/bfin.h (NOTICE_UPDATE_CC): Remove.
parent
e4c707d2
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
gcc/config/bfin/bfin.h
+0
-2
0 additions, 2 deletions
gcc/config/bfin/bfin.h
with
0 additions
and
2 deletions
gcc/config/bfin/bfin.h
+
0
−
2
View file @
b50ccaf6
...
@@ -786,8 +786,6 @@ typedef struct {
...
@@ -786,8 +786,6 @@ typedef struct {
|| GET_CODE (X) == LABEL_REF \
|| GET_CODE (X) == LABEL_REF \
|| (GET_CODE (X) == CONST && symbolic_reference_mentioned_p (X)))
|| (GET_CODE (X) == CONST && symbolic_reference_mentioned_p (X)))
#define NOTICE_UPDATE_CC(EXPR, INSN) 0
/* Max number of bytes we can move from memory to memory
/* Max number of bytes we can move from memory to memory
in one reasonably fast instruction. */
in one reasonably fast instruction. */
#define MOVE_MAX UNITS_PER_WORD
#define MOVE_MAX UNITS_PER_WORD
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment