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
d3111037
Commit
d3111037
authored
Mar 29, 1999
by
Craig Burley
Committed by
Craig Burley
Mar 29, 1999
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Clarify -fcheck-memory-usage
From-SVN: r26057
parent
fdb1833a
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
16 additions
and
7 deletions
+16
-7
gcc/ChangeLog
+5
-0
gcc/invoke.texi
+11
-7
No files found.
gcc/ChangeLog
View file @
d3111037
Mon
Mar
29
15
:
11
:
10
1999
Craig
Burley
<
craig
@jcb
-
sc
.
com
>
*
invoke
.
texi
(
Code
Gen
Options
)
:
Attempt
to
clarify
-
fcheck
-
memory
-
usage
.
Minor
edits
to
-
fprefix
-
function
-
name
.
Mon
Mar
29
20
:
52
:
47
1999
J
"orn Rennecke <amylaar@cygnus.co.uk>
* loop.c (maybe_eliminate_biv): For libcalls that set a giv, skip to
...
...
gcc/invoke.texi
View file @
d3111037
...
...
@@ -6060,17 +6060,22 @@ Generate extra code to check each memory access. GNU CC will generate
code
that
is
suitable
for
a
detector
of
bad
memory
accesses
such
as
@file{
Checker
}
.
You
must
also
specify
this
option
when
you
compile
functions
you
call
that
have
side
effects
.
If
you
do
not
,
you
may
get
erroneous
messages
from
the
detector
.
Normally
,
you
should
compile
all
your
code
with
this
option
.
Normally
,
you
should
compile
all
,
or
none
,
of
your
code
with
this
option
.
If
you
do
mix
code
compiled
with
and
without
this
option
,
you
must
ensure
that
all
code
that
has
side
effects
and
that
is
called
by
code
compiled
with
this
option
is
,
itself
,
compiled
with
this
option
.
If
you
do
not
,
you
might
get
erroneous
messages
from
the
detector
.
If
you
use
functions
from
a
library
that
have
side
-
effects
(
such
as
@code{
read
}
),
you
m
ay
not
be
able
to
recompile
the
library
and
@code{
read
}
),
you
m
ight
not
be
able
to
recompile
the
library
and
specify
this
option
.
In
that
case
,
you
can
enable
the
@samp{
-
fprefix
-
function
-
name
}
option
,
which
requests
GNU
CC
to
encapsulate
your
code
and
make
other
functions
look
as
if
they
were
compiled
with
@samp{
-
fcheck
-
memory
-
usage
}
.
This
is
done
by
calling
``
stubs
''
,
which
are
provided
by
the
detector
.
If
you
cannot
find
or
build
stubs
for
every
function
you
call
,
you
m
ay
have
to
specify
stubs
for
every
function
you
call
,
you
m
ight
have
to
specify
@samp{
-
fcheck
-
memory
-
usage
}
without
@samp{
-
fprefix
-
function
-
name
}
.
If
you
specify
this
option
,
you
can
not
use
the
@code{
asm
}
or
...
...
@@ -6095,7 +6100,7 @@ These calls would be similar to those done in the stubs described above.
Request
GNU
CC
to
add
a
prefix
to
the
symbols
generated
for
function
names
.
GNU
CC
adds
a
prefix
to
the
names
of
functions
defined
as
well
as
functions
called
.
Code
compiled
with
this
option
and
code
compiled
without
the
option
can
'
t
be
linked
together
,
unless
or
stubs
are
used
.
without
the
option
can
'
t
be
linked
together
,
unless
stubs
are
used
.
If
you
compile
the
following
code
with
@samp{
-
fprefix
-
function
-
name
}
@example
...
...
@@ -6104,7 +6109,6 @@ void
foo
(
int
a
)
@{
return
bar
(
a
+
5
)
;
@
}
@end
example
...
...
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