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
0b4d5576
Commit
0b4d5576
authored
Jan 24, 2006
by
Mark Mitchell
Committed by
Mark Mitchell
Jan 24, 2006
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
* semantics.c: Remove outdated comment.
From-SVN: r110164
parent
e7b9eb2c
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
5 additions
and
5 deletions
+5
-5
gcc/cp/ChangeLog
+4
-0
gcc/cp/semantics.c
+1
-5
No files found.
gcc/cp/ChangeLog
View file @
0b4d5576
2006-01-24 Mark Mitchell <mark@codesourcery.com>
* semantics.c: Remove outdated comment.
2006-01-23 Volker Reichelt <reichelt@igpm.rwth-aachen.de>
* cp-tree.h (do_poplevel): Remove prototype.
...
...
gcc/cp/semantics.c
View file @
0b4d5576
...
...
@@ -51,11 +51,7 @@
/* There routines provide a modular interface to perform many parsing
operations. They may therefore be used during actual parsing, or
during template instantiation, which may be regarded as a
degenerate form of parsing. Since the current g++ parser is
lacking in several respects, and will be reimplemented, we are
attempting to move most code that is not directly related to
parsing into this file; that will make implementing the new parser
much easier since it will be able to make use of these routines. */
degenerate form of parsing. */
static
tree
do_poplevel
(
tree
);
static
tree
maybe_convert_cond
(
tree
);
...
...
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