OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Remove some obsolete comments 

While working on complex number support, I found a couple of
apparently obsolete coments.  This removes them.

2020-03-07  Tom Tromey  <tom@tromey.com>

	* valops.c (value_literal_complex): Remove obsolete comment.
	* gdbtypes.h (enum type_code) <TYPE_CODE_FLT>: Remove obsolete
	comment.
This commit is contained in:
Tom Tromey 2020-03-07 07:53:42 -07:00
parent 190e5fc8b3
commit e893257635
3 changed files with 8 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
gdb/ChangeLog
View File

@ -1,3 +1,9 @@
2020-03-07 Tom Tromey <tom@tromey.com>
* valops.c (value_literal_complex): Remove obsolete comment.
* gdbtypes.h (enum type_code) <TYPE_CODE_FLT>: Remove obsolete
comment.
2020-03-06 Simon Marchi <simon.marchi@polymtl.ca>
* infrun.h: Forward-declare thread_info.

4
gdb/gdbtypes.h
View File

@ -120,9 +120,7 @@ enum type_code
TYPE_CODE_FUNC, /**< Function type */
TYPE_CODE_INT, /**< Integer type */
/* * Floating type. This is *NOT* a complex type. Beware, there
are parts of GDB which bogusly assume that TYPE_CODE_FLT can
mean complex. */
/* * Floating type. This is *NOT* a complex type. */
TYPE_CODE_FLT,
/* * Void type. The length field specifies the length (probably

4
gdb/valops.c
View File

@ -3856,9 +3856,7 @@ value_slice (struct value *array, int lowbound, int length)
/* Create a value for a FORTRAN complex number. Currently most of the
time values are coerced to COMPLEX*16 (i.e. a complex number
composed of 2 doubles. This really should be a smarter routine
that figures out precision intelligently as opposed to assuming
doubles. FIXME: fmb */
composed of 2 doubles. */
struct value *
value_literal_complex (struct value *arg1,