On Fri, Dec 14, 2007 at 02:47:02PM -0800, Doug Kwan (關振德) wrote:
> The new encoding format I am proposing fall between DW_ATE_lo_user and
> DW_ATE_hi_user. So they are vendor extensions. Currently gcc uses
> DW_ATE_lo_user, which collides with an HP vendor extension.
If we already have one vendor
The new encoding format I am proposing fall between DW_ATE_lo_user and
DW_ATE_hi_user. So they are vendor extensions. Currently gcc uses
DW_ATE_lo_user, which collides with an HP vendor extension.
-Doug
2007/12/14, Daniel Jacobowitz <[EMAIL PROTECTED]>:
> On Fri, Dec 14, 2007 at 02:30:36PM -0800
On Fri, Dec 14, 2007 at 02:30:36PM -0800, Doug Kwan (關振德) wrote:
> Is there anything I need to do in addition to changing gcc? Are
> there people I should talk to? And what documentation should be
> updated? Currently gdb (I checked 6.7) does not support complex
> integer properly. So it needs to
Hi,
I am working on the gcc LTO project and I found that gcc does not
generate sufficient debugging information for complex integer types.
Currently gcc uses encoding DW_ATE_lo_user ( 0x80) for complex integer
types but that 1) clashes with an HP extension and 2) does not
distinguish between c
