From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Hilfinger To: Elena Zannoni Cc: gdb-patches@sources.redhat.com Subject: Re: Question concerning comment in symtab.h Date: Wed, 16 May 2001 12:50:00 -0000 Message-id: <200105161949.MAA15140@tully.CS.Berkeley.EDU> References: <15106.55172.717482.640326@kwikemart.cygnus.com> X-SW-Source: 2001-05/msg00334.html >This code in valops.c was added to handle HP's native compiler. I am >really tempted to just remove it, because it breaks function calls >with function pointers as parameters for all the cases in which gcc is >not used. I am going to submit a patch to get rid of this code. >If I do that, I think the only remaining use of gcc_compile_flag >outside of the symbol readers is in generic_use_struct_convention in >values.c, and it is used to distinguish between different versions of >gcc (specifically 2.0 to 2.3.3, vs. all the others). I wonder if this >could be eliminated as well. Well, as a matter of fact, I was grubbing around here precisely in order to enhance support for debugging native-HP-compiled code---WHAT an odd coincidence. Are you saying you DON'T want to support HP- native-compiled code, or are you saying that we should move to a better approach? If, as I hope, you mean the latter, could we agree on The Right Way to do this? The specific problem I am struggling with is that GCC does not entirely conform to HP's ABI for stack-unwinding info (specifically, it slightly misuses the SAVE_SP bit: see also previous messages from me on this). Paul Hilfinger