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
580fb356
Commit
580fb356
authored
Dec 13, 2002
by
Jim Wilson
Committed by
Jim Wilson
Dec 13, 2002
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Doc fix for PR 1621.
* doc/extend.texi (Complex Numbers): Update info on debug info. From-SVN: r60101
parent
b4f145f3
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
8 additions
and
7 deletions
+8
-7
gcc/ChangeLog
+4
-0
gcc/doc/extend.texi
+4
-7
No files found.
gcc/ChangeLog
View file @
580fb356
2002
-
12
-
13
Jim
Wilson
<
wilson
@redhat
.
com
>
*
doc
/
extend
.
texi
(
Complex
Numbers
)
:
Update
info
on
debug
info
.
2002
-
12
-
13
Kazu
Hirata
<
kazu
@cs
.
umass
.
edu
>
*
config
/
h8300
/
h8300
.
md
(
addhi3_h8300
)
:
Remove
the
last
...
...
gcc/doc/extend.texi
View file @
580fb356
...
...
@@ -1224,17 +1224,14 @@ provided as built-in functions by GCC@.
GCC can allocate complex automatic variables in a noncontiguous
fashion; it'
s
even
possible
for
the
real
part
to
be
in
a
register
while
the
imaginary
part
is
on
the
stack
(
or
vice
-
versa
).
None
of
the
supported
debugging
info
formats
has
a
way
to
represent
noncontiguous
allocation
like
this
,
so
GCC
describes
a
noncontiguous
complex
variable
as
if
it
were
two
separate
variables
of
noncomplex
type
.
the
imaginary
part
is
on
the
stack
(
or
vice
-
versa
).
Only
the
DWARF2
debug
info
format
can
represent
this
,
so
use
of
DWARF2
is
recommended
.
If
you
are
using
the
stabs
debug
info
format
,
GCC
describes
a
noncontiguous
complex
variable
as
if
it
were
two
separate
variables
of
noncomplex
type
.
If
the
variable
's actual name is @code{foo}, the two fictitious
variables are named @code{foo$real} and @code{foo$imag}. You can
examine and set these two fictitious variables with your debugger.
A future version of GDB will know how to recognize such pairs and treat
them as a single variable with a complex type.
@node Hex Floats
@section Hex Floats
@cindex hex floats
...
...
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