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
7e97e174
Commit
7e97e174
authored
Jan 23, 2014
by
Arnaud Charlet
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Minor editing.
From-SVN: r206989
parent
8bdc02c2
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
9 additions
and
8 deletions
+9
-8
gcc/ada/gnat_rm.texi
+9
-8
No files found.
gcc/ada/gnat_rm.texi
View file @
7e97e174
...
@@ -4249,14 +4249,15 @@ pragma Linker_Section (
...
@@ -4249,14 +4249,15 @@ pragma Linker_Section (
@end smallexample
@end smallexample
@noindent
@noindent
@var{LOCAL_NAME} must refer to an object that is declared at the library
@var{LOCAL_NAME} must refer to an object or a subprogram that is
level. This pragma specifies the name of the linker section for the given
declared at the library level. This pragma specifies the name of the
entity. It is equivalent to @code{__attribute__((section))} in GNU C and
linker section for the given entity. It is equivalent to
causes @var{LOCAL_NAME} to be placed in the @var{static_string_EXPRESSION}
@code{__attribute__((section))} in GNU C and causes @var{LOCAL_NAME} to
section of the executable (assuming the linker doesn'
t
rename
the
section
).
be placed in the @var{static_string_EXPRESSION} section of the
executable (assuming the linker doesn'
t
rename
the
section
).
The
compiler
normally
places
library
-
level
objects
in
standard
sections
depending
on
their
type
:
procedures
and
functions
generally
go
in
the
The
compiler
normally
places
library
-
level
entities
in
standard
sections
depending
on
the
class
:
procedures
and
functions
generally
go
in
the
@
code
{.
text
}
section
,
initialized
variables
in
the
@
code
{.
data
}
section
@
code
{.
text
}
section
,
initialized
variables
in
the
@
code
{.
data
}
section
and
uninitialized
variables
in
the
@
code
{.
bss
}
section
.
and
uninitialized
variables
in
the
@
code
{.
bss
}
section
.
...
...
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