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
3754c8fe
Commit
3754c8fe
authored
Oct 28, 2015
by
Richard Henderson
Committed by
Richard Henderson
Oct 28, 2015
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
* tree-eh.c (mark_reachable_handlers): Fix typo in assert.
From-SVN: r229497
parent
7bc2eabe
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
5 additions
and
1 deletions
+5
-1
gcc/ChangeLog
+4
-0
gcc/tree-eh.c
+1
-1
No files found.
gcc/ChangeLog
View file @
3754c8fe
2015
-
10
-
28
Richard
Henderson
<
rth
@
redhat
.
com
>
*
tree
-
eh
.
c
(
mark_reachable_handlers
):
Fix
typo
in
assert
.
2015
-
10
-
05
Senthil
Kumar
Selvaraj
<
senthil_kumar
.
selvaraj
@
atmel
.
com
>
2015
-
10
-
05
Senthil
Kumar
Selvaraj
<
senthil_kumar
.
selvaraj
@
atmel
.
com
>
PR
target
/
67839
PR
target
/
67839
gcc/tree-eh.c
View file @
3754c8fe
...
@@ -3857,7 +3857,7 @@ mark_reachable_handlers (sbitmap *r_reachablep, sbitmap *lp_reachablep)
...
@@ -3857,7 +3857,7 @@ mark_reachable_handlers (sbitmap *r_reachablep, sbitmap *lp_reachablep)
tree
rt
=
gimple_call_arg
(
stmt
,
i
);
tree
rt
=
gimple_call_arg
(
stmt
,
i
);
HOST_WIDE_INT
ri
=
tree_to_shwi
(
rt
);
HOST_WIDE_INT
ri
=
tree_to_shwi
(
rt
);
gcc_assert
(
ri
=
(
int
)
ri
);
gcc_assert
(
ri
=
=
(
int
)
ri
);
bitmap_set_bit
(
r_reachable
,
ri
);
bitmap_set_bit
(
r_reachable
,
ri
);
}
}
break
;
break
;
...
...
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