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
162f2c72
Commit
162f2c72
authored
Apr 20, 2009
by
Arnaud Charlet
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update comments.
From-SVN: r146372
parent
ff2e7c1e
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
15 additions
and
19 deletions
+15
-19
gcc/ada/par-prag.adb
+0
-1
gcc/ada/sinfo.ads
+15
-18
No files found.
gcc/ada/par-prag.adb
View file @
162f2c72
...
@@ -264,7 +264,6 @@ begin
...
@@ -264,7 +264,6 @@ begin
if Present (Pragma_Argument_Associations (Pragma_Node)) then
if Present (Pragma_Argument_Associations (Pragma_Node)) then
Arg_Node := Arg1;
Arg_Node := Arg1;
while Arg_Node /= Empty loop
while Arg_Node /= Empty loop
Arg_Count := Arg_Count + 1;
Arg_Count := Arg_Count + 1;
...
...
gcc/ada/sinfo.ads
View file @
162f2c72
...
@@ -6562,11 +6562,10 @@ package Sinfo is
...
@@ -6562,11 +6562,10 @@ package Sinfo is
-- in the declarations of the innermost enclosing block as specified
-- in the declarations of the innermost enclosing block as specified
-- in RM section 5.1 (3).
-- in RM section 5.1 (3).
-- The Defining_Identifier is the actual identifier for the
-- The Defining_Identifier is the actual identifier for the statement
-- statement identifier. Note that the occurrence of the label
-- identifier. Note that the occurrence of the label is a reference, NOT
-- is a reference, NOT the defining occurrence. The defining
-- the defining occurrence. The defining occurrence occurs at the head
-- occurrence occurs at the head of the innermost enclosing
-- of the innermost enclosing block, and is represented by this node.
-- block, and is represented by this node.
-- Note: from the grammar, this might better be called an implicit
-- Note: from the grammar, this might better be called an implicit
-- statement identifier declaration, but the term we choose seems
-- statement identifier declaration, but the term we choose seems
...
@@ -6574,11 +6573,10 @@ package Sinfo is
...
@@ -6574,11 +6573,10 @@ package Sinfo is
-- called labels in both cases (i.e. when used in labels, and when
-- called labels in both cases (i.e. when used in labels, and when
-- used as the identifiers of blocks and loops).
-- used as the identifiers of blocks and loops).
-- Note: although this is logically a semantic node, since it does
-- Note: although this is logically a semantic node, since it does not
-- not correspond directly to a source syntax construction, these
-- correspond directly to a source syntax construction, these nodes are
-- nodes are actually created by the parser in a post pass done just
-- actually created by the parser in a post pass done just after parsing
-- after parsing is complete, before semantic analysis is started (see
-- is complete, before semantic analysis is started (see Par.Labl).
-- the Par.Labl subunit in file par-labl.adb).
-- Sprint syntax: labelname : label;
-- Sprint syntax: labelname : label;
...
@@ -6594,19 +6592,18 @@ package Sinfo is
...
@@ -6594,19 +6592,18 @@ package Sinfo is
-- Itype_Reference --
-- Itype_Reference --
---------------------
---------------------
-- This node is used to create a reference to an Itype. The only
-- This node is used to create a reference to an Itype. The only purpose
-- purpose is to make sure that the Itype is defined if this is the
-- is to make sure the Itype is defined if this is the first reference.
-- first reference.
-- A typical use of this node is when an Itype is to be referenced in
-- A typical use of this node is when an Itype is to be referenced in
-- two branches of an
if
statement. In this case it is important that
-- two branches of an
IF
statement. In this case it is important that
-- the first use of the Itype not be inside the conditional, since
-- the first use of the Itype not be inside the conditional, since
then
--
then it might not be defined if the wrong branch of the if is
--
it might not be defined if the other branch of the IF is taken, in
-- t
aken in t
he case where the definition generates elaboration code.
-- the case where the definition generates elaboration code.
-- The Itype field points to the referenced Itype
-- The Itype field points to the referenced Itype
--
s
print syntax: reference itype-name
--
S
print syntax: reference itype-name
-- N_Itype_Reference
-- N_Itype_Reference
-- Sloc points to the node generating the reference
-- Sloc points to the node generating the reference
...
...
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