mirror of
https://github.com/darlinghq/darling-gdb.git
synced 2025-02-15 15:08:41 +00:00
* values.c (USE_STRUCT_RETURN): Only use gcc wierdness for gcc1.
This commit is contained in:
parent
6755c51e93
commit
9925b92861
@ -1,5 +1,7 @@
|
||||
Tue Apr 6 09:54:29 1993 Jim Kingdon (kingdon@cygnus.com)
|
||||
|
||||
* values.c (USE_STRUCT_RETURN): Only use gcc wierdness for gcc1.
|
||||
|
||||
* xcoffread.c (read_xcoff_symtab): Deal correctly with symbols of
|
||||
exactly 8 characters.
|
||||
|
||||
|
10
gdb/values.c
10
gdb/values.c
@ -1484,9 +1484,17 @@ value_being_returned (valtype, retbuf, struct_return)
|
||||
|
||||
On most machines, the struct convention is used unless we are
|
||||
using gcc and the type is of a special size. */
|
||||
/* As of about 31 Mar 93, GCC was changed to be compatible with the
|
||||
native compiler. GCC 2.3.3 was the last release that did it the
|
||||
old way. Since gcc2_compiled was not changed, we have no
|
||||
way to correctly win in all cases, so we just do the right thing
|
||||
for gcc1 and for gcc2 after this change. Thus it loses for gcc
|
||||
2.0-2.3.3. This is somewhat unfortunate, but changing gcc2_compiled
|
||||
would cause more chaos than dealing with some struct returns being
|
||||
handled wrong. */
|
||||
#if !defined (USE_STRUCT_CONVENTION)
|
||||
#define USE_STRUCT_CONVENTION(gcc_p, type)\
|
||||
(!((gcc_p) && (TYPE_LENGTH (value_type) == 1 \
|
||||
(!((gcc_p == 1) && (TYPE_LENGTH (value_type) == 1 \
|
||||
|| TYPE_LENGTH (value_type) == 2 \
|
||||
|| TYPE_LENGTH (value_type) == 4 \
|
||||
|| TYPE_LENGTH (value_type) == 8 \
|
||||
|
Loading…
x
Reference in New Issue
Block a user